Triple
T9956094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | magister militum |
E195449
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman military rank |
C23723
|
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: late Roman military rank Context triple: [magister militum, instanceOf, late Roman military rank]
-
A.
Roman military office
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Roman military commander
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.
-
E.
historical military rank
A historical military rank is a formally defined level of authority and responsibility within past armed forces, reflecting the hierarchical structure, duties, and social status of military personnel in a specific historical context.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:46 p.m.