Triple
T3294284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XLVII |
E69174
|
entity |
| Predicate | powerOutageDurationMinutes |
P12075
|
FINISHED |
| Object | 34 |
—
|
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: 34 | Statement: [Super Bowl XLVII, powerOutageDurationMinutes, 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerOutageDurationMinutes Context triple: [Super Bowl XLVII, powerOutageDurationMinutes, 34]
-
A.
periodInPowerEnd
Indicates the point in time when an entity’s tenure or period in power comes to an end.
-
B.
interruptionDuration
chosen
Indicates the length of time for which an ongoing activity, process, or state is temporarily halted or disrupted.
-
C.
lostPowerDuring
Indicates that an entity ceased to have electrical or functional power at some time during a specified event or interval.
-
D.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
E.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb07661748190bf57469e101c5283 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.