Triple
T28718945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauretania |
E730037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | client kingdom of the Roman Empire |
C9381
|
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: client kingdom of the Roman Empire Context triple: [Mauretania, instanceOf, client kingdom of the Roman Empire]
-
A.
client state of the Roman Empire
chosen
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.
-
B.
King of Rome
The King of Rome is a conceptual class representing the sovereign ruler of the ancient Roman Kingdom, embodying supreme political, religious, and military authority prior to the establishment of the Roman Republic.
-
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.
client state of the Roman Republic
A client state of the Roman Republic was a formally independent polity that, through treaties or coercion, accepted Roman supremacy in foreign policy, military support, and often internal affairs in exchange for protection and limited autonomy.
-
E.
area of ancient Rome
An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:52 a.m.