Triple
T24659628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 NFC Championship Game |
E610500
|
entity |
| Predicate | typeOfPlayoffGame |
P8299
|
FINISHED |
| Object | conference championship |
—
|
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: conference championship | Statement: [1979 NFC Championship Game, typeOfPlayoffGame, conference championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPlayoffGame Context triple: [1979 NFC Championship Game, typeOfPlayoffGame, conference championship]
-
A.
playoffRound
chosen
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
B.
playoffResult
Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
-
C.
officiatedGameType
Indicates the type or category of game that an official (e.g., referee or umpire) presided over.
-
D.
playoffBracketSide
Indicates which side of a playoff tournament bracket (e.g., left/right or top/bottom half) a given team, match, or participant is placed on.
-
E.
playoffConference
Indicates that a team participates in the playoffs within a specific conference (e.g., Eastern or Western) of a sports league.
- 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_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:34 a.m.