Triple
T14074766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 NFC Wild Card game vs New Orleans Saints |
E338702
|
entity |
| Predicate | homeTeamDivisionTitle |
P90860
|
FINISHED |
| Object | 2010 NFC West 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: 2010 NFC West champions | Statement: [2011 NFC Wild Card game vs New Orleans Saints, homeTeamDivisionTitle, 2010 NFC West champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamDivisionTitle Context triple: [2011 NFC Wild Card game vs New Orleans Saints, homeTeamDivisionTitle, 2010 NFC West champions]
-
A.
homeTeamDivisionOrConference
chosen
Indicates the division or conference to which the home team in a game or matchup belongs.
-
B.
awayTeamDivision
Indicates the competitive division or grouping to which the away team belongs in a league or tournament structure.
-
C.
winningTeamDivision
Indicates the division to which the team that won a given game, match, or competition belongs.
-
D.
team1Division
Indicates the competitive division or grouping in which the first team participates or is classified.
-
E.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving 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_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. |
Created at: April 9, 2026, 10:21 p.m.