What this category’s data looks like
Data sources for the oil and gas extraction domain include real-time monitoring data from internal oilfield operation systems, exploration reports publicly released by natural resource authorities, research papers from authoritative industry journals, and public datasets from third-party oil and gas service institutions. Three update cadences apply:
- Real-time monitoring data updates every 15 minutes
- Monthly operation reports are released by the 5th of the following month
- Annual industry reports are released by the end of March of the following year
Individual documents include fields such as well site identifier, logging depth, lithology type, permeability, and oil saturation. Logging depth is measured in meters, permeability is measured in millidarcys, and oil saturation is recorded as a decimal value.
What constraints do these characteristics impose on the "citation source and traceability" workflow
The high-frequency updates of real-time monitoring data require the traceability function to match the data collection timestamp, to avoid citing expired monitoring results. The multi-dimensional field document structure requires traceability to accurately locate the paragraph containing a specific field; returning the full document does not meet this requirement. Dispersed data sources require the traceability function to support unified display of cross-source identifiers, and field mapping rules must be configured to adapt to naming differences across data sources. The presence of long documents requires the traceability function to support paragraph-level positioning display, avoiding returning redundant full text and improving the readability of traceability information.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
reference_paragraph_mode | Enable paragraph-level traceability | Adapt to scenarios where oil and gas extraction documents are long and require precise positioning of specific data segments, avoiding returning full-page documents as citations |
source_field_mapping | Configure well ID, permeability, and logging depth as unified traceability fields | Adapt to the multi-field feature of oil and gas extraction data, unify field display formats across different data sources |
recall_top_k | Top 8 entries | Oil and gas extraction data has many field dimensions, requiring sufficient recall volume to cover relevant data sources and avoid missing key information |
similarity_threshold | 0.75–0.85 | Filter low-match traceability results and avoid introducing unrelated drilling logs or reports |
PARSE_FILE_TIMEOUT_SECONDS | 300 seconds | Adapt to the parsing duration of long documents such as complete drilling logs, avoiding traceability failures caused by parsing timeouts |
enable_real_time_source_sync | Enable real-time synchronization | Adapt to the high-frequency updates of real-time monitoring data, ensuring that traceability data matches the source data timestamp |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis, and it is recommended to test against your own samples before finalizing settings.
Three common configuration mistakes
- Phenomenon: The exported knowledge base backup only contains the overall knowledge base file, and cannot be exported split by well ID or business category. Cause: The
source_export_group_ruleparameter is not configured, and the function of exporting split by business dimension is not enabled. - Phenomenon: The
source_infofield in results returned by the question answering API call is empty. Cause: Theenable_source_referenceconfiguration is not enabled, or the recall configuration is not associated with the source data index. - Phenomenon: A 404 status code is returned when accessing the original knowledge base document link. Cause: The source file path mapping for the nginx proxy is not configured, causing the original link to fail to point to the real storage location.
How to verify correct configuration
- Upload a single drilling log document, initiate a query containing fields from this document, and check whether the citation module in the returned results displays accurate paragraph positions and corresponding field information.
- Call the question answering interface, check whether the returned results contain the preset traceability field content, and confirm that the
source_infofield exists and the format meets the configuration requirements. - After configuring the nginx proxy, manually access the original knowledge base document link to confirm that the corresponding document loads normally with no access errors.
- Upload a real-time updated monitoring data document, initiate a query, and check whether the cited timestamp matches the collection time of the source data.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.