Triple
T35658361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1920 NFL season |
E1030357
|
entity |
| Predicate | championshipDeterminationMethod |
P92786
|
FINISHED |
| Object | league standings |
—
|
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: league standings | Statement: [1920 NFL season, championshipDeterminationMethod, league standings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipDeterminationMethod Context triple: [1920 NFL season, championshipDeterminationMethod, league standings]
-
A.
determinesChampionBy
Indicates that one entity establishes or decides which entity is the champion, typically as the outcome of a competition or evaluation.
-
B.
hasChampionshipDetermination
chosen
Indicates that an entity specifies the rules, criteria, or process by which a championship winner is determined.
-
C.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
-
D.
championshipFor
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
-
E.
championshipStatus
Indicates the competitive or title-holding state of an entity within a championship or league context.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:05 p.m.