Triple
T28722661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limes Romanus |
E730136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman border fortification |
C26007
|
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 border fortification Context triple: [Limes Romanus, instanceOf, Roman border fortification]
-
A.
Roman frontier
chosen
The Roman frontier was the shifting boundary zone of the Roman Empire, marked by fortifications, military roads, and garrisoned settlements that controlled movement, trade, and defense between Roman territories and neighboring peoples.
-
B.
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.
-
C.
Roman settlement
A Roman settlement is a community established under Roman rule, characterized by Roman architecture, infrastructure, administration, and cultural practices integrated with local traditions.
-
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.
military fortification system
A military fortification system is an integrated network of defensive structures, obstacles, and support facilities designed to protect territory, forces, and strategic assets from enemy attack.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:54 a.m.