Triple
T2061063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Parkside neighborhood parkways |
E45789
|
entity |
| Predicate | streetLayoutType |
P1019
|
FINISHED |
| Object | parkway |
—
|
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: parkway | Statement: [The Parkside neighborhood parkways, streetLayoutType, parkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetLayoutType Context triple: [The Parkside neighborhood parkways, streetLayoutType, parkway]
-
A.
streetGridOrientation
Indicates the predominant directional alignment or pattern of streets within a given area or city layout.
-
B.
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.
-
C.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
D.
hasTreeLinedStreets
Indicates that the streets in a given area are lined or bordered with trees along their sides.
-
E.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d0ecf08190aec20338a6ba9911 |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.