Triple
T24952236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Parade |
E624370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Melbourne |
C49332
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: street in Melbourne Context triple: [Royal Parade, instanceOf, street in Melbourne]
-
A.
street
A street is a public thoroughfare in an urban or suburban area, typically bordered by buildings, that facilitates vehicular and pedestrian movement and often supports various social and commercial activities.
-
B.
street in Marseille
A street in Marseille is a public urban thoroughfare within the city of Marseille, typically lined with Mediterranean-style buildings, local shops, and cultural landmarks that reflect the city's coastal and multicultural character.
-
C.
street in Lyon
A street in Lyon is a public urban thoroughfare within the city of Lyon, France, typically lined with buildings, shops, and residences, and serving as a conduit for pedestrian and vehicular movement as well as local social and commercial activity.
-
D.
street in Montreal
A street in Montreal is a public urban thoroughfare that reflects the city’s blend of historic European-influenced architecture, diverse neighborhoods, bilingual culture, and seasonal climate, supporting vehicular, pedestrian, and often cycling traffic.
-
E.
street in Chicago
A street in Chicago is a public urban thoroughfare within the city’s grid system that facilitates vehicular and pedestrian movement while connecting residential, commercial, and cultural areas.
- F. None of above. chosen
Provenance (1 batch)
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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 5:57 a.m.