Triple
T12615681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1968 NFL Championship |
E301244
|
entity |
| Predicate | ClevelandBrownsConference |
P14283
|
FINISHED |
| Object | NFL Century Division champion |
—
|
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: NFL Century Division champion | Statement: [1968 NFL Championship, ClevelandBrownsConference, NFL Century Division champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ClevelandBrownsConference Context triple: [1968 NFL Championship, ClevelandBrownsConference, NFL Century Division champion]
-
A.
AFCChampionshipOpponent
Indicates that one team was the opposing team faced in an AFC Championship game by another team.
-
B.
NFLTeam
chosen
Indicates a relationship where an entity is identified as a professional American football team that competes in the National Football League.
-
C.
AFCChampionshipGameWinner
Indicates the team that won the AFC Championship Game in a given season or year.
-
D.
NFLDebutTeam
Indicates the team for which a player made their first appearance in an NFL game.
-
E.
AFCChampionDivision
Indicates that a team has won the championship title of a specific division within the American Football Conference (AFC).
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.