Triple
T24659611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 NFC Championship Game |
E610500
|
entity |
| Predicate | visitingTeamPlayoffSeed |
P18175
|
FINISHED |
| Object | No. 3 seed in NFC |
—
|
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: No. 3 seed in NFC | Statement: [1979 NFC Championship Game, visitingTeamPlayoffSeed, No. 3 seed in NFC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitingTeamPlayoffSeed Context triple: [1979 NFC Championship Game, visitingTeamPlayoffSeed, No. 3 seed in NFC]
-
A.
visitingTeamConferenceSeed
Indicates the ranking or seed assigned to the visiting team within its conference for a given competition or season.
-
B.
playoffSeed
chosen
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
C.
homeTeamSeed
Indicates the ranking or seed assigned to the home team within a tournament or competition bracket.
-
D.
losingTeamSeed
Indicates the tournament seed or ranking assigned to the team that lost in a given game or matchup.
-
E.
firstSeasonPlayoffSeed
Indicates the playoff seeding position a team received in its first season of participation.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.