Triple
T35859610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1938 World Series |
E1036908
|
entity |
| Predicate | locationOfYankeeStadium |
P206077
|
FINISHED |
| Object | Bronx, New York City |
E8102
|
NE 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: Bronx, New York City | Statement: [1938 World Series, locationOfYankeeStadium, Bronx, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfYankeeStadium Context triple: [1938 World Series, locationOfYankeeStadium, Bronx, New York City]
-
A.
YankeesHomeBallpark
Indicates that a specified ballpark serves as the home stadium for the New York Yankees.
-
B.
cityOfEbbetsField
Indicates the city in which Ebbets Field is located.
-
C.
ballparkLocatedOn
Indicates that a ballpark is situated on or directly associated with a specific street, road, or thoroughfare.
-
D.
oneOfOldestMLBStadiums
Indicates that the subject is among the oldest Major League Baseball stadiums still in existence or use.
-
E.
serviceToYankeeStadium
Indicates that there is transportation service or a route that goes to or serves Yankee Stadium.
- F. None of above. chosen
Provenance (5 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6eb8cb481909b5b3658a3229995 |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.