Triple
T2101114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonine Wall |
E37094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman frontier fortification |
C875
|
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 frontier fortification Context triple: [Antonine Wall, instanceOf, Roman frontier fortification]
-
A.
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.
-
B.
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.
-
C.
Numidian settlement
A Numidian settlement is a community or town established by the ancient Numidian people of North Africa, typically characterized by fortified hilltop locations, mixed pastoral-agricultural economies, and cultural influences from both indigenous Berber traditions and Mediterranean civilizations.
-
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.
line of fortifications
chosen
A line of fortifications is a connected series of defensive structures, such as walls, trenches, and strongpoints, designed to protect a territory or position by forming a continuous or coordinated barrier against 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.