Triple
T35859611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1938 World Series |
E1036908
|
entity |
| Predicate | locationOfWrigleyField |
P206078
|
FINISHED |
| Object | Chicago, Illinois |
E818754
|
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: Chicago, Illinois | Statement: [1938 World Series, locationOfWrigleyField, Chicago, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfWrigleyField Context triple: [1938 World Series, locationOfWrigleyField, Chicago, Illinois]
-
A.
ballparkLocatedOn
Indicates that a ballpark is situated on or directly associated with a specific street, road, or thoroughfare.
-
B.
DetroitHomeBallpark
Indicates that a sports team’s primary home ballpark is located in Detroit.
-
C.
cityOfDodgerStadium
Indicates the city in which Dodger Stadium is located.
-
D.
cityOfMinuteMaidPark
Indicates the city in which Minute Maid Park is located.
-
E.
formerHomeBallparkLocation
Indicates the location where an entity’s home ballpark used to be situated before it moved or was replaced.
- 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_6a389c03b900819099674f6db2d59500 |
completed | June 22, 2026, 2:20 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.