Triple
T8924187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optimates |
E212499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman political faction |
C24207
|
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 faction Context triple: [Optimates, instanceOf, Roman political faction]
-
A.
Roman political movement
chosen
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.
-
B.
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.
-
C.
Florentine political faction
A Florentine political faction is a historically rooted group within Florence’s civic life that organized around shared social, economic, or ideological interests to compete for power and influence in the city’s government and public affairs.
-
D.
medieval political faction
A medieval political faction is an organized group of nobles, clergy, or urban elites who align around shared interests, loyalties, or claims to power, competing and negotiating within the feudal and dynastic structures of the Middle Ages.
-
E.
Roman chariot racing faction
A Roman chariot racing faction was a highly organized, color-coded team and fan association that owned horses and chariots, employed drivers, and inspired intense political, social, and sometimes violent rivalries in the circus.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.