Triple
T20616694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Buckeyes |
E506585
|
entity |
| Predicate | leagueAffiliationEnd |
P71729
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [Cleveland Buckeyes, leagueAffiliationEnd, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueAffiliationEnd Context triple: [Cleveland Buckeyes, leagueAffiliationEnd, 1950]
-
A.
affiliationEndedWith
chosen
Indicates that a previously existing affiliation or association between entities has come to an end at a specific point in time or under certain conditions.
-
B.
leagueDisbanded
Indicates that a sports league or competitive organization has formally ceased operations and no longer exists as an active entity.
-
C.
leagueAffiliationHistory
Indicates the historical sequence of leagues or organizations with which an entity has been affiliated over time.
-
D.
leagueAffiliationManaged
Indicates that one entity manages, oversees, or administers the league affiliation of another entity.
-
E.
careerEndTeam
Indicates the team or organization with which an individual concluded their professional career.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadbb3ac81908145f57fd6a94256 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.