Triple
T6645701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 NFC Championship Game |
E150693
|
entity |
| Predicate | homeTeamConferenceSeed |
P18175
|
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: [1980 NFC Championship Game, homeTeamConferenceSeed, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamConferenceSeed Context triple: [1980 NFC Championship Game, homeTeamConferenceSeed, 1]
-
A.
homeTeamSeed
Indicates the ranking or seed assigned to the home team within a tournament or competition bracket.
-
B.
regularSeasonTopSeedConference
Indicates that an entity was the highest-ranked (top-seeded) team in its conference during the regular season.
-
C.
playoffSeed
chosen
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
D.
awayTeamConference
Indicates the athletic conference to which the away (visiting) team belongs in a sporting event.
-
E.
eligibleSeedsPerConference
Indicates the specific tournament seed positions within each conference that qualify as eligible under the defined rules or criteria.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2 p.m.