Triple
T35658333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1920 NFL season |
E1030357
|
entity |
| Predicate | leagueLaterRenamedAs |
P27053
|
FINISHED |
| Object | National Football League |
—
|
NE NERFINISHED |
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: National Football League | Statement: [1920 NFL season, leagueLaterRenamedAs, National Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueLaterRenamedAs Context triple: [1920 NFL season, leagueLaterRenamedAs, National Football League]
-
A.
leagueRenamedAs
chosen
Indicates that a sports league has changed its official name to a new one.
-
B.
laterLeagueName
Indicates that an entity’s league name was changed to a different (later) league name at some point in time.
-
C.
renamingOfLeagueOccurredIn
Indicates that an official change of name for a sports league took place during a specified time or event.
-
D.
leaguePredecessor
Indicates that one league existed before and was replaced or succeeded by another league in an organizational or historical sequence.
-
E.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.