Triple
T25794616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kern River Formation |
E649644
|
entity |
| Predicate | discoveryAsOilReservoir |
P73791
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Kern River Formation, discoveryAsOilReservoir, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryAsOilReservoir Context triple: [Kern River Formation, discoveryAsOilReservoir, late 19th century]
-
A.
discoveredAsPetroleumPlay
chosen
Indicates that the subject was identified or recognized specifically as a viable petroleum exploration or production opportunity.
-
B.
containsOilField
Indicates that one entity geographically includes or encompasses an oil field within its boundaries.
-
C.
nearbyOilField
Indicates that one location is situated close to an oil field.
-
D.
hasHydrocarbonTraps
Indicates the presence of geological structures or conditions that can accumulate and retain hydrocarbons such as oil or gas.
-
E.
discoveryOfOre
Indicates the event or relationship in which a particular ore deposit is found, identified, or recognized, typically linking the discoverer, the ore, and the location or time of discovery.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 6:28 a.m.