Triple
T3411140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Small World Salute to 25 Years of the Super Bowl |
E71895
|
entity |
| Predicate | performedOnDate |
P29412
|
FINISHED |
| Object | 1991-01-27 |
—
|
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: 1991-01-27 | Statement: [A Small World Salute to 25 Years of the Super Bowl, performedOnDate, 1991-01-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedOnDate Context triple: [A Small World Salute to 25 Years of the Super Bowl, performedOnDate, 1991-01-27]
-
A.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
-
B.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
playedOnDate
chosen
Indicates that an event or activity (such as a game, performance, or match) occurred on a specific calendar date.
-
E.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on another entity.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9094b2881909262e58a470ed9d0 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.