Triple
T34894624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rome (French-occupied) |
E1006396
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political history of Rome |
C24030
|
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: political history of Rome Context triple: [Rome (French-occupied), instanceOf, political history of Rome]
-
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.
history of the ancient world
The history of the ancient world examines the civilizations, cultures, events, and interactions of human societies from the earliest recorded times to the fall of the Western Roman Empire.
-
C.
Roman historiography
Roman historiography is the body of historical writing produced in ancient Rome that blends factual record, rhetorical craft, and moral or political interpretation to narrate Rome’s past and shape its collective identity.
-
D.
ancient Italo-Roman relations
Ancient Italo-Roman relations encompass the political, military, economic, and cultural interactions between Rome and the diverse Italic peoples of the Italian peninsula from early expansion through the Social War and the integration of Italy into the Roman state.
-
E.
historical polities
chosen
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.