Triple
T10979668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Highlanders |
E259466
|
entity |
| Predicate | officialNameChangeToYankees |
P96430
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [New York Highlanders, officialNameChangeToYankees, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameChangeToYankees Context triple: [New York Highlanders, officialNameChangeToYankees, 1913]
-
A.
ballparkNameChangeYear
Indicates the year in which a ballpark’s official name was changed.
-
B.
leagueRenamedAs
Indicates that a sports league has changed its official name to a new one.
-
C.
YankeesPreviousTitle
Indicates that the subject entity is the immediately preceding championship title held by the New York Yankees before the object entity.
-
D.
endedAsStLouisCardinals
Indicates that an entity’s tenure, career, or existence concluded while it was associated with or known as the St. Louis Cardinals.
-
E.
affiliationStartYearWithNewYorkYankees
Indicates the year in which an entity’s affiliation or association with the New York Yankees began.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772e97cf88190a65dab3ec4e5f7f3 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.