Triple
T23581609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinzie Street |
E582219
|
entity |
| Predicate | hasCrossingStructureNearby |
P49266
|
FINISHED |
| Object | Kinzie Street Railroad Bridge |
—
|
NE NERFINISHED |
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: Kinzie Street Railroad Bridge | Statement: [Kinzie Street, hasCrossingStructureNearby, Kinzie Street Railroad Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossingStructureNearby Context triple: [Kinzie Street, hasCrossingStructureNearby, Kinzie Street Railroad Bridge]
-
A.
hasNearbyCrossingPoint
chosen
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
B.
hasAtGradeCrossingNearby
Indicates that one entity (typically a location or segment) has a nearby at-grade crossing where two transportation paths intersect at the same level.
-
C.
hasCrossingPoint
Indicates that two or more entities intersect or share at least one common point in space or along their paths.
-
D.
crossesNear
Indicates that one entity passes across the path or area of another entity at a location that is close to, but not directly intersecting, the other entity.
-
E.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02cf4e0819094ff4e406cda270d |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:39 p.m.