Triple
T14979258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civitas Batavorum |
E373532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman civitas |
C5442
|
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 civitas Context triple: [Civitas Batavorum, instanceOf, Roman civitas]
-
A.
Roman town
chosen
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.
-
B.
Roman citizen
A Roman citizen is an individual legally recognized as a member of the Roman state, endowed with specific rights, protections, and civic responsibilities under Roman law.
-
C.
Roman dynasty
A Roman dynasty is a succession of rulers from the same family or lineage who governed the Roman state over a continuous period, shaping its political, social, and cultural development.
-
D.
ancient Roman
An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
-
E.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:51 a.m.