Triple
T5932684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Agrippa |
E131973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman road network |
C3822
|
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 network Context triple: [Via Agrippa, instanceOf, Roman road network]
-
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.
Inca road system
The Inca road system was an extensive, sophisticated network of paved and unpaved routes spanning thousands of kilometers across the Andes, designed to connect and administer the vast Inca Empire through efficient communication, trade, and military movement.
-
C.
road network
chosen
A road network is an interconnected system of roads, intersections, and related infrastructure that enables the movement of vehicles and pedestrians between different locations.
-
D.
ancient Roman structure
An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
-
E.
road infrastructure
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4 p.m.