Triple
T22928666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spindletop oil field |
E569375
|
entity |
| Predicate | enteredDecline |
P19208
|
FINISHED |
| Object | after 1902 |
—
|
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: after 1902 | Statement: [Spindletop oil field, enteredDecline, after 1902]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredDecline Context triple: [Spindletop oil field, enteredDecline, after 1902]
-
A.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
B.
declinedAround
Indicates that something decreased in value, intensity, or quantity in the time period surrounding a specified point or event.
-
C.
declineOrEnd
Indicates that a relationship, process, or state is either decreasing in intensity or coming to a complete end.
-
D.
endedOrDeclinedAfter
Indicates that one entity’s involvement, status, or offer concluded or was rejected following the occurrence or completion of another specified event or condition.
-
E.
declineAfter
chosen
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
- 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.