Triple
T1103526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bowl Most Valuable Player Award |
E25434
|
entity |
| Predicate | ceremonyOccurs |
P14854
|
FINISHED |
| Object | immediately after the Super Bowl game |
—
|
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: immediately after the Super Bowl game | Statement: [Super Bowl Most Valuable Player Award, ceremonyOccurs, immediately after the Super Bowl game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyOccurs Context triple: [Super Bowl Most Valuable Player Award, ceremonyOccurs, immediately after the Super Bowl game]
-
A.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
B.
ceremonyIncludes
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
-
C.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
-
D.
ceremonyHeldOn
Indicates that a specific ceremony took place on a particular date or day.
-
E.
ceremonyTiming
chosen
Indicates the temporal relationship specifying when a ceremony occurs or is scheduled to occur.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c375848190baec4d534f489616 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b7472c848190b0643872f67084a2 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.