Triple
T4422034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Kickoff Game |
E95121
|
entity |
| Predicate | typicalHostTeamStatus |
P55884
|
FINISHED |
| Object | reigning Super Bowl champion franchise |
—
|
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: reigning Super Bowl champion franchise | Statement: [NFL Kickoff Game, typicalHostTeamStatus, reigning Super Bowl champion franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHostTeamStatus Context triple: [NFL Kickoff Game, typicalHostTeamStatus, reigning Super Bowl champion franchise]
-
A.
finalHostTeam
Indicates that a team is designated as the host team for the final match or final stage of a competition.
-
B.
ownedTeamHomeState
Indicates that the owning entity’s home or primary location is in the same state as the team’s home state.
-
C.
team1State
Indicates the current status or condition of the first team in a given context or event.
-
D.
team2State
Indicates the current status or condition of the second team in a given context or event.
-
E.
hostTeam
Indicates that one team serves as the host (home) team in relation to a particular game, match, or event.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554a0e7c8190b704d00d07b1857d |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.