Triple
T5650380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madison Street |
E124491
|
entity |
| Predicate | roleInStreetGrid |
P43747
|
FINISHED |
| Object | primary east–west axis |
—
|
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: primary east–west axis | Statement: [Madison Street, roleInStreetGrid, primary east–west axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInStreetGrid Context triple: [Madison Street, roleInStreetGrid, primary east–west axis]
-
A.
locatedBetweenStreets
Indicates that something is situated between two specified streets, with its position bounded or defined by those streets.
-
B.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with the other entity.
-
C.
roadSystemRole
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
-
D.
streetFunction
chosen
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
-
E.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d4ca788190b20168b20cb1d030 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.