Triple
T6064329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burdigala |
E135117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | settlement in Gaul |
C4966
|
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: settlement in Gaul Context triple: [Burdigala, instanceOf, settlement in Gaul]
-
A.
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.
-
B.
Count of Soissons
The Count of Soissons was a medieval noble title associated with the governance and control of the County of Soissons in northern France, often held by influential aristocratic families involved in regional and royal politics.
-
C.
settlement in Scotland
A settlement in Scotland is any inhabited place, ranging from small hamlets and villages to towns and cities, recognized as a distinct community within the country’s geographic and administrative landscape.
-
D.
Roman settlement
chosen
A Roman settlement is a community established under Roman rule, characterized by Roman architecture, infrastructure, administration, and cultural practices integrated with local traditions.
-
E.
Celtic settlement
A Celtic settlement is a community or habitation site established by Celtic peoples, typically characterized by fortified hilltops, roundhouses, and a material culture reflecting Celtic social, economic, and religious practices.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:10 p.m.