Triple
T28580627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 NFC Championship |
E723363
|
entity |
| Predicate | homeTeamConferenceTitleCountAfterGame |
P166881
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [2009 NFC Championship, homeTeamConferenceTitleCountAfterGame, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamConferenceTitleCountAfterGame Context triple: [2009 NFC Championship, homeTeamConferenceTitleCountAfterGame, 1]
-
A.
homeTeamTitleCountAfterMatch
Indicates the total number of titles the home team has accumulated after the completion of the referenced match.
-
B.
homeTeamConferenceChampionshipAppearancesToDate
Indicates the number of conference championship appearances the home team has made up to the current point in time.
-
C.
homeLeagueRecordAfterGame
Indicates the updated performance record of a team in its home league immediately following a specific game.
-
D.
scoringTeamConference
Indicates the athletic conference to which the team that scored belongs.
-
E.
playsHomeConferenceGamesIn
Indicates that a team plays its home conference games at a specified location or venue.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:14 a.m.