Triple
T22044580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diversey Avenue |
E544726
|
entity |
| Predicate | hasCityRouteNumber |
P1864
|
FINISHED |
| Object | 2400 North |
—
|
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: 2400 North | Statement: [Diversey Avenue, hasCityRouteNumber, 2400 North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityRouteNumber Context triple: [Diversey Avenue, hasCityRouteNumber, 2400 North]
-
A.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
B.
hasRouteNumberingRole
Indicates that an entity participates in the assignment, management, or designation of route numbers for a transportation route or network.
-
C.
hasRoadNumberStatus
Indicates that a road or route is associated with a specific status regarding its assigned road number (e.g., active, reserved, retired, or provisional).
-
D.
routeNumber
chosen
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
E.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1282d5bb08190849d5084962bf3a5 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:25 p.m.