Triple
T23649914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conventus of Lugdunum |
E584138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman judicial district |
C32966
|
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 judicial district Context triple: [conventus of Lugdunum, instanceOf, Roman judicial district]
-
A.
Roman province
A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
-
B.
regio of Rome under Augustus
A regio of Rome under Augustus was one of the fourteen administrative districts into which the emperor reorganized the city for more efficient governance, public order, and urban management.
-
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.
council in Roman Gaul
A council in Roman Gaul was a regional assembly of civic elites and representatives from Gallic cities that met under Roman authority to discuss local affairs, express loyalty to the emperor, and coordinate provincial religious and political activities.
-
E.
ancient district
chosen
An ancient district is a historically defined administrative or geographic area that existed in antiquity, often characterized by distinct political, cultural, or social functions within a larger civilization.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:49 p.m.