Triple
T13411247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nijmegen Hunerberg |
E320091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military site |
C25570
|
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 site Context triple: [Nijmegen Hunerberg, instanceOf, Roman military site]
-
A.
Roman military camp
chosen
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.
-
B.
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.
-
C.
Roman town
A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
-
D.
Roman frontier
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.
-
E.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:35 p.m.