Triple
T31701606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1930 NFL season |
E809069
|
entity |
| Predicate | teamLeftLeagueAfterSeason |
P172437
|
FINISHED |
| Object | Minneapolis Red Jackets |
—
|
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: Minneapolis Red Jackets | Statement: [1930 NFL season, teamLeftLeagueAfterSeason, Minneapolis Red Jackets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLeftLeagueAfterSeason Context triple: [1930 NFL season, teamLeftLeagueAfterSeason, Minneapolis Red Jackets]
-
A.
leagueMergerAfterSeasonWith
Indicates that two or more leagues merged into a single league following the completion of a specified season.
-
B.
successorTeamLeague
Indicates that one sports league is the direct successor to another for a given team’s participation or affiliation.
-
C.
leagueFoundedSeason
Indicates the season during which a particular league was established or founded.
-
D.
laterLeagueName
Indicates that an entity’s league name was changed to a different (later) league name at some point in time.
-
E.
losingLeagueTeam
Indicates that a team is the one that lost in a particular league game or competition.
- F. None of above. chosen
Provenance (4 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:12 p.m.