Triple
T9162333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmwood |
E219855
|
entity |
| Predicate | hasCentralStreet |
P86862
|
FINISHED |
| Object | Elmwood Avenue |
—
|
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: Elmwood Avenue | Statement: [Elmwood, hasCentralStreet, Elmwood Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralStreet Context triple: [Elmwood, hasCentralStreet, Elmwood Avenue]
-
A.
hasMainStreet
Indicates that a place or locality possesses a primary street commonly recognized as its main thoroughfare.
-
B.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
C.
hasStreetLayoutCenteredOn
Indicates that the spatial organization or pattern of streets in one place is arranged with a particular feature or location as its central focus or reference point.
-
D.
isDowntownCoreOf
Indicates that a location constitutes the central, most urbanized and commercially dense area of a larger city or metropolitan region.
-
E.
hasNotableStreet
Indicates that an entity is associated with a particular street that is considered notable or significant.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2c1a9881909b7100b6e436386d |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:21 p.m.