Triple
T1502236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl XLVIII |
E33819
|
entity |
| Predicate | firstScoreType |
P28113
|
FINISHED |
| Object | safety |
—
|
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: safety | Statement: [Super Bowl XLVIII, firstScoreType, safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstScoreType Context triple: [Super Bowl XLVIII, firstScoreType, safety]
-
A.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
B.
firstSeriesCode
Indicates that an entity is identified as the initial or primary series within a sequence, referenced by a specific code.
-
C.
firstTier
Indicates that one entity occupies the highest or primary level, rank, or priority relative to others in a hierarchical structure.
-
D.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
-
E.
primaryType
chosen
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:24 p.m.