Triple
T8001041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centurion |
E186248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman military rank |
C22226
|
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 rank Context triple: [Centurion, instanceOf, Roman military rank]
-
A.
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.
-
B.
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.
-
C.
army rank
chosen
An army rank is a formal level of authority and responsibility within a military hierarchy that defines a soldier’s position, duties, and chain-of-command relationships.
-
D.
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.
-
E.
military rank structure
A military rank structure is a hierarchical system that organizes service members into levels of authority and responsibility, defining command relationships, roles, and progression within the armed forces.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:17 p.m.