Triple
T1225021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Comiskey Park |
E26306
|
entity |
| Predicate | successorFacilityLocation |
P26023
|
FINISHED |
| Object | across 35th Street |
—
|
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: across 35th Street | Statement: [Old Comiskey Park, successorFacilityLocation, across 35th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorFacilityLocation Context triple: [Old Comiskey Park, successorFacilityLocation, across 35th Street]
-
A.
successorFacility
Indicates that one facility directly follows and replaces another in function, ownership, or operation.
-
B.
successorBuildingOnSite
Indicates that one building directly replaces another on the same physical site or location.
-
C.
successorInCity
Indicates that one entity directly follows or replaces another in holding a particular role, position, or function within the same city.
-
D.
successorAgencyFunction
Indicates that one agency has taken over or continues the functions, responsibilities, or roles previously carried out by another agency.
-
E.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be382c4081909238c18b805352a7 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd3140688190ac6e24de157fd61e |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:47 p.m.