Triple
T9957242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Militaris |
E195474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman trade route |
C26542
|
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 trade route Context triple: [Via Militaris, instanceOf, Roman trade route]
-
A.
transalpine trade route
A transalpine trade route is a transportation corridor that crosses the Alps to facilitate the movement of goods, people, and cultural exchange between regions on either side of the mountain range.
-
B.
ancient route listing
An ancient route listing is a documented catalog of historical travel paths, roads, or trade routes, often detailing their locations, connections, and significance in past civilizations.
-
C.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
-
D.
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.
-
E.
transoceanic trade network
A transoceanic trade network is a system of interconnected maritime routes, ports, merchants, and institutions that facilitate the large-scale exchange of goods, people, capital, and ideas across oceans between distant regions of the world.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:46 p.m.