Triple
T24649804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterkant (Paramaribo waterfront) |
E610216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Paramaribo |
C49464
|
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 Paramaribo Context triple: [Waterkant (Paramaribo waterfront), instanceOf, street in Paramaribo]
-
A.
street in San Juan, Puerto Rico
A street in San Juan, Puerto Rico is a public urban thoroughfare within the city’s historic or modern districts, lined with local residences, businesses, and cultural landmarks that facilitate vehicular and pedestrian movement.
-
B.
road in Jamaica
A road in Jamaica is a paved or unpaved transportation route that connects towns, cities, and rural areas across the island, accommodating vehicles, pedestrians, and local traffic within Jamaica’s tropical environment and cultural context.
-
C.
street in Quito
A street in Quito is a public urban thoroughfare within Ecuador’s capital city, shaped by its Andean topography, colonial and modern architecture, and the daily movement of pedestrians and vehicles.
-
D.
street in Lima
A street in Lima is a public urban thoroughfare that facilitates vehicular and pedestrian movement while supporting the city’s commercial, residential, and social activities within the diverse neighborhoods of Peru’s capital.
-
E.
street in Riga
A street in Riga is a public urban thoroughfare within Latvia’s capital city, typically lined with a mix of historic and modern buildings, and serving as a route for pedestrian and vehicular traffic as well as local commerce and social activity.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:33 a.m.