Triple
T36109690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Browns |
E1044458
|
entity |
| Predicate | wonAAFCChampionship |
P28353
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Cleveland Browns, wonAAFCChampionship, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonAAFCChampionship Context triple: [Cleveland Browns, wonAAFCChampionship, 1946]
-
A.
AAFCChampionship
chosen
Indicates a competitive event or title match that determines the champion within the AAFC (All-America Football Conference).
-
B.
NFCChampionshipGame
Indicates the relationship in which a game serves as the championship matchup determining the National Football Conference (NFC) champion in a given season.
-
C.
AFCChampionshipGame
Indicates a game that serves as the championship matchup determining the winner of the American Football Conference (AFC).
-
D.
AFCChampionDivision
Indicates that a team has won the championship title of a specific division within the American Football Conference (AFC).
-
E.
NFCChampionshipOpponent
Indicates that one team was the opposing team faced in the NFC Championship game by the other team.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.