Triple
T6766508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Army officers |
E154733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military rank holder |
C449
|
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: military rank holder Context triple: [British Army officers, instanceOf, military rank holder]
-
A.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
B.
supreme military rank
A supreme military rank is the highest possible position in a nation's armed forces hierarchy, typically held by a single individual with ultimate authority over all military operations and strategy.
-
C.
paramilitary rank
A paramilitary rank is a hierarchical title or position within an organized, non-military armed group that mirrors military ranking structures to define authority, responsibility, and command.
-
D.
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.
-
E.
military office
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support military operations.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:12 p.m.