Triple
T31762470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dux Romanorum |
E810718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military title |
C10598
|
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 military title Context triple: [dux Romanorum, instanceOf, Roman military title]
-
A.
ancient Roman title
An ancient Roman title is a formal designation or rank used in Roman society and government to denote an individual's official role, status, or authority within the political, military, religious, or social hierarchy.
-
B.
Roman military office
A Roman military office is an administrative and command position within the Roman armed forces responsible for organizing, directing, and managing soldiers, resources, and military operations.
-
C.
Roman military honor
A Roman military honor is a formal recognition, often in the form of decorations, titles, or privileges, awarded to soldiers or commanders for exceptional bravery, leadership, or service in the Roman armed forces.
-
D.
Roman official
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
-
E.
Roman military commander
chosen
A Roman military commander is a high-ranking officer responsible for leading legions, planning and executing campaigns, maintaining discipline, and securing Rome’s political and territorial interests through organized warfare.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:31 p.m.