Triple
T33868167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shock |
E868114
|
entity |
| Predicate | finalSeasonInTulsa |
P196670
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Shock, finalSeasonInTulsa, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSeasonInTulsa Context triple: [Shock, finalSeasonInTulsa, 2015]
-
A.
penultimateSeasonOf
Indicates that one season is the second-to-last season in the sequence of seasons of a given series or show.
-
B.
finalSeasonInNewOrleans
Indicates that the referenced season is the last one taking place in New Orleans.
-
C.
finalSeasonTitle
Indicates that the object is the title given to the final season of the subject.
-
D.
endYearInOklahomaCity
Indicates that the entity’s final or ending year of activity, existence, or relevance occurred in Oklahoma City.
-
E.
finalSeasonInEvansville
Indicates that an entity’s final season or concluding period of activity took place in Evansville.
- F. None of above. chosen
Provenance (4 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: May 1, 2026, 1:47 a.m.