Triple
T28237494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senatus Populusque Romanus dedication |
E711917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman state formula |
C54574
|
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 state formula Context triple: [Senatus Populusque Romanus dedication, instanceOf, Roman state formula]
-
A.
Roman Republican institution
A Roman Republican institution is a political, legal, or social structure that operated within the Roman Republic’s mixed constitution to distribute authority, regulate civic life, and balance power among magistrates, assemblies, and the Senate.
-
B.
Roman official
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
-
C.
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.
-
D.
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.
-
E.
roman
A Roman is a member or characteristic of the ancient civilization of Rome, encompassing its people, culture, architecture, governance, and influence on Western history.
- F. None of above. chosen
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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:56 p.m.