Triple
T14074767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 NFC Wild Card game vs New Orleans Saints |
E338702
|
entity |
| Predicate | awayTeamStatus |
P112716
|
FINISHED |
| Object | defending Super Bowl champions |
—
|
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: defending Super Bowl champions | Statement: [2011 NFC Wild Card game vs New Orleans Saints, awayTeamStatus, defending Super Bowl champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awayTeamStatus Context triple: [2011 NFC Wild Card game vs New Orleans Saints, awayTeamStatus, defending Super Bowl champions]
-
A.
awayTeam
Indicates that an entity is designated as the visiting or non-home team in a competitive event or match.
-
B.
stateOfHomeTeam2
Indicates the current status or condition of the second home team in a given context or event.
-
C.
typicalHostTeamStatus
Indicates the usual or standard status or role that a team holds when acting as the host in an event or competition.
-
D.
homeStateTeamStatus
Indicates the status or condition of a team in relation to its designated home state.
-
E.
awayTeamCity
Indicates the city that the away (visiting) team is from in a sporting event or competition.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.