Triple
T17569715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheberghan |
E427903
|
entity |
| Predicate | nearbyNaturalResource |
P2856
|
FINISHED |
| Object | natural gas fields |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: natural gas fields | Statement: [Sheberghan, nearbyNaturalResource, natural gas fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyNaturalResource Context triple: [Sheberghan, nearbyNaturalResource, natural gas fields]
-
A.
nearNaturalRegion
Indicates that one entity is located close to a specified natural region or area in geographic space.
-
B.
naturalResources
chosen
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
C.
nearGeologicalSite
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
D.
nearbyBasin
Indicates that one basin is located close to another basin in space.
-
E.
lakeTypeNearby
Indicates that one entity is located near another entity that is classified as a particular type of lake.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592fe8408190bd8fed1920ab3601 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.