Triple
T23726551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coalinga Oil Field |
E586292
|
entity |
| Predicate | significantOilBoom |
P81073
|
FINISHED |
| Object | early 20th 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: early 20th century | Statement: [Coalinga Oil Field, significantOilBoom, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantOilBoom Context triple: [Coalinga Oil Field, significantOilBoom, early 20th century]
-
A.
firstOil
Indicates that the subject is the first entity to discover, produce, or commercially extract oil in relation to the object (such as a region, field, or context).
-
B.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
C.
isPartOfOilRichRegion
Indicates that an entity is located within or belongs to a geographic area characterized by abundant oil resources.
-
D.
significantDevelopment
chosen
Indicates a development, change, or event that has substantial impact or importance within a given context or process.
-
E.
isOilIndustryHub
Indicates that a location serves as a central focal point for activities, infrastructure, and operations related to the oil industry.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b915a888819088e92f99711e8120 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:08 p.m.