Triple
T8312689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itinerary II of the Antonine Itinerary |
E194628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman road itinerary |
C703
|
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: Roman road itinerary Context triple: [Itinerary II of the Antonine Itinerary, instanceOf, Roman road itinerary]
-
A.
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.
-
B.
road in Italy
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.
-
C.
historic road
chosen
A historic road is a transportation route of significant age and cultural, economic, or political importance, preserved or recognized for its role in shaping historical events, trade, or settlement patterns.
-
D.
transportation route
A transportation route is a defined path or corridor used to move people or goods between locations via one or more modes of transport.
-
E.
road network
A road network is an interconnected system of roads, intersections, and related infrastructure that enables the movement of vehicles and pedestrians between different locations.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.