Triple
T31061086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 NFL season |
E791540
|
entity |
| Predicate | NFCChampionshipSite |
P170705
|
FINISHED |
| Object | Giants Stadium |
—
|
NE NERFINISHED |
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: Giants Stadium | Statement: [2000 NFL season, NFCChampionshipSite, Giants Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NFCChampionshipSite Context triple: [2000 NFL season, NFCChampionshipSite, Giants Stadium]
-
A.
NFCChampionshipGame
Indicates the relationship in which a game serves as the championship matchup determining the National Football Conference (NFC) champion in a given season.
-
B.
NFCChampionshipOpponent
Indicates that one team was the opposing team faced in the NFC Championship game by the other team.
-
C.
NFCChampionshipGameLoser
Indicates the team that lost a given NFC Championship Game in American football.
-
D.
NFCChampionshipGameWinner
Indicates the team that won the NFC Championship Game in a given season or instance.
-
E.
NFCChampionshipGameScore
Indicates the final point totals achieved by each team in a specific NFC Championship Game matchup.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695774a2481908b1fc2ff44544db6 |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9:01 p.m.