Triple
T22044597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diversey Avenue |
E544726
|
entity |
| Predicate | hasCoordinateSystemPosition |
P10142
|
FINISHED |
| Object | 2400 North in Chicago grid system |
—
|
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 in Chicago grid system | Statement: [Diversey Avenue, hasCoordinateSystemPosition, 2400 North in Chicago grid system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinateSystemPosition Context triple: [Diversey Avenue, hasCoordinateSystemPosition, 2400 North in Chicago grid system]
-
A.
usesCoordinateRepresentation
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
-
B.
hasCoordinates
chosen
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
C.
hasCoordinateRole
Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
-
D.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
E.
hasCoordinatesType
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
- 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.