Triple
T2071759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saw Mill River Parkway |
E44828
|
entity |
| Predicate | isUrbanConnector |
P1495
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Saw Mill River Parkway, isUrbanConnector, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanConnector Context triple: [Saw Mill River Parkway, isUrbanConnector, yes]
-
A.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
B.
isUrbanized
Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
-
C.
isUrbanPark
Indicates that a location is designated and used as a public park within an urban or metropolitan area.
-
D.
hasUrbanFunction
Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
-
E.
hasUrbanFeature
chosen
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba0d20bc8190b19a32157f8b1607 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.