Triple
T25849018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1982 NFC Championship Game |
E651148
|
entity |
| Predicate | homeTeamCurrentName |
P123266
|
FINISHED |
| Object | Washington Commanders |
—
|
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: Washington Commanders | Statement: [1982 NFC Championship Game, homeTeamCurrentName, Washington Commanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamCurrentName Context triple: [1982 NFC Championship Game, homeTeamCurrentName, Washington Commanders]
-
A.
currentNameOfTeam
chosen
Indicates that the specified name is the team’s current official name (as opposed to a past or future name).
-
B.
homeTeamCurrentSuccessor
Indicates that one team is the immediate next home team in a sequence of home-team assignments or events.
-
C.
hostTeamFranchise
Indicates that a team franchise is serving as the host team in a given game or event.
-
D.
currentFranchiseNameSince
Indicates the date or time from which the entity has been operating under its current franchise name.
-
E.
homeTeamPreviousTitleSeason
Indicates the season in which the home team most recently won a title prior to the current event or season.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60239fb6881908503759ddd6b3fb1 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:57 a.m.