Triple
T36845460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | legio |
E910532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman military unit |
C23903
|
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 military unit Context triple: [legio, instanceOf, ancient Roman military unit]
-
A.
Roman territorial unit
A Roman territorial unit is an administrative division of land within the Roman state, defined for purposes such as governance, taxation, military organization, and legal jurisdiction.
-
B.
ancient Roman paramilitary corps
An ancient Roman paramilitary corps is a semi-military organization operating alongside or outside the formal legions, tasked with security, policing, or specialized combat roles in support of Roman state authority.
-
C.
ancient cavalry unit
An ancient cavalry unit is a military formation composed of mounted soldiers trained to fight from horseback, used for rapid movement, shock attacks, reconnaissance, and flanking maneuvers on the battlefield.
-
D.
aspect of the Roman army
An aspect of the Roman army is a distinct component, practice, structure, or role within Rome’s military system that contributed to its organization, effectiveness, and operations.
-
E.
Roman legion
chosen
A Roman legion is a large, highly organized military unit of the ancient Roman army, typically composed of several thousand heavily armed infantry supported by cavalry and specialized troops.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.