Triple
T13562367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via dei Pettinari |
E323939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Rome |
C22784
|
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: road in Rome Context triple: [Via dei Pettinari, instanceOf, road in Rome]
-
A.
road in Italy
chosen
A road in Italy is a public or private transportation route within Italian territory, designed for vehicular and pedestrian travel and governed by Italian traffic laws and infrastructure standards.
-
B.
road in Berlin
A road in Berlin is a public thoroughfare within the city’s urban network that facilitates vehicular, bicycle, and pedestrian movement while integrating with Berlin’s historical layout, public transit, and zoning infrastructure.
-
C.
ancient Roman street
An ancient Roman street is a paved public thoroughfare, typically constructed of stone blocks with raised sidewalks, drainage systems, and often lined with shops, houses, and public buildings, facilitating movement, trade, and social interaction within Roman cities.
-
D.
road in Shanghai
A road in Shanghai is a transportation corridor within the city’s dense urban fabric that supports mixed traffic—vehicles, buses, bicycles, and pedestrians—while integrating local infrastructure, commercial activity, and municipal regulations specific to Shanghai.
-
E.
road in Baltimore
A road in Baltimore is a public thoroughfare within the city’s transportation network that facilitates vehicular, bicycle, and pedestrian movement while connecting neighborhoods, businesses, and regional routes.
- F. None of above.
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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:47 p.m.