Triple
T30161733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historia Romana |
E766683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman history |
C13617
|
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 history Context triple: [Historia Romana, instanceOf, ancient Roman history]
-
A.
ancient Roman
An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
-
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
chosen
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.
area of ancient Rome
An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
-
E.
ancient Roman literature
Ancient Roman literature encompasses the body of written works produced in Latin (and some Greek) by Roman authors, reflecting the political, social, philosophical, and artistic life of Rome from its early Republic through the Imperial period.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:22 p.m.