Triple
T30519758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Republic (Caesarian faction) |
E776662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman political entity |
C24217
|
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 entity Context triple: [Roman Republic (Caesarian faction), instanceOf, Roman political entity]
-
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.
ancient political entity
An ancient political entity is a historically situated, organized community or state that exercised authority, governance, and control over a defined territory and population in antiquity.
-
C.
Roman political alliance
chosen
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.
-
D.
Roman regio
A Roman regio was an administrative district or region within ancient Rome or its territories, used for organizing governance, census, and urban planning.
-
E.
Roman province
A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:17 p.m.