Triple
T16926705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midtown Mile |
E410592
|
entity |
| Predicate | streetscapeType |
P108672
|
FINISHED |
| Object | urban streetscape |
—
|
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: urban streetscape | Statement: [Midtown Mile, streetscapeType, urban streetscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetscapeType Context triple: [Midtown Mile, streetscapeType, urban streetscape]
-
A.
streetscapeStyle
chosen
Indicates the characteristic visual and design style that defines the overall appearance and layout of a street and its surrounding public realm.
-
B.
isPartOfStreetscape
Indicates that something forms a component or element within the overall layout or visual composition of a streetscape.
-
C.
streetOrAreaType
Indicates the specific kind or classification of a street or area (such as avenue, boulevard, district, or zone) associated with an entity.
-
D.
skylineType
Indicates the general visual or structural character of a skyline, such as its dominant form, density, or profile.
-
E.
partOfUrbanLayout
Indicates that one entity is a component or constituent element within the overall structure or organization of an urban 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdf2dcd881909798bd245e18c599 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.