Triple
T22928647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spindletop oil field |
E569375
|
entity |
| Predicate | gusherOccurred |
P106888
|
FINISHED |
| Object | 1901-01-10 |
—
|
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: 1901-01-10 | Statement: [Spindletop oil field, gusherOccurred, 1901-01-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gusherOccurred Context triple: [Spindletop oil field, gusherOccurred, 1901-01-10]
-
A.
gasReleased
Indicates that a gas is emitted or discharged from a source into its surrounding environment.
-
B.
explosionOccurred
Indicates that an explosion event has taken place at a specific time and/or location.
-
C.
erupted
Indicates that a volcano or similar geological feature suddenly expelled lava, ash, gas, or other material in a violent outburst.
-
D.
associatedBlowout
chosen
Indicates a relationship where one event, object, or condition is linked to or results in a specific blowout event (such as a sudden, uncontrolled release or failure).
-
E.
laterBlownUpTo
Indicates that one entity is subsequently destroyed or blown up at a later time relative to another referenced event or state.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180db6db88190bc8efb691dcdfdba |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.