Triple
T9957241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Militaris |
E195474
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military road |
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 military road Context triple: [Via Militaris, instanceOf, Roman military road]
-
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.
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.
-
C.
Roman military camp
A Roman military camp is a temporary or permanent fortified encampment laid out in a standardized, highly organized grid pattern to house, protect, and support Roman troops during campaigns.
-
D.
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.
-
E.
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.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:46 p.m.