Triple
T22040281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbis Romanus |
E544619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman political concept |
C7736
|
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 political concept Context triple: [Orbis Romanus, instanceOf, Roman political concept]
-
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 political movement
A Roman political movement is a collective effort by individuals or groups in ancient Rome to influence governance, laws, and public policy in pursuit of specific social, economic, or ideological goals.
-
C.
component of the Roman state
chosen
A component of the Roman state is any institutional, social, or political element—such as magistracies, assemblies, the Senate, legal frameworks, or provincial administrations—that collectively structured and maintained Roman governance and public life.
-
D.
Roman Republican-era figure
A Roman Republican-era figure is an individual who lived and was active during the Roman Republic (c. 509–27 BCE), typically participating in its political, military, social, or cultural life.
-
E.
Roman political alliance
A Roman political alliance is a formal or informal partnership between individuals, factions, or states in ancient Rome formed to consolidate power, advance mutual political interests, and influence governance and decision-making.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:25 p.m.