Triple
T8722064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major General of the Army (historical French role) |
E207034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical military office |
C2499
|
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: historical military office Context triple: [Major General of the Army (historical French role), instanceOf, historical military office]
-
A.
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.
-
B.
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.
-
C.
military officer
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.
-
D.
military appointment
chosen
A military appointment is an official position or duty assigned to a service member within the armed forces, defining their role, responsibilities, and authority.
-
E.
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.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.