Triple
T23148948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servian Constitution (traditional) |
E578269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman constitutional reform |
C45911
|
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: ancient Roman constitutional reform Context triple: [Servian Constitution (traditional), instanceOf, ancient Roman constitutional reform]
-
A.
roman politique
Un roman politique est une œuvre de fiction centrée sur les enjeux, mécanismes et conflits du pouvoir au sein de la société, explorant idéologies, institutions et luttes sociales à travers une intrigue narrative.
-
B.
Roman reformer
A Roman reformer is an individual in ancient Rome who sought to change political, social, or economic structures through legislation, public advocacy, or institutional innovation to address perceived injustices or inefficiencies.
-
C.
ancient republic
An ancient republic is a form of government in classical antiquity where political power is held by a body of citizens and their elected or appointed representatives, rather than by a monarch.
-
D.
Athenian reform program
Athenian reform program: A series of political, legal, and social changes in ancient Athens aimed at broadening citizen participation, reducing aristocratic power, and stabilizing the democratic polis.
-
E.
Roman Republican institution
chosen
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.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:01 p.m.