Triple
T8721989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chef d’état-major de l’Armée de terre |
E207032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French military position |
C18940
|
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: French military position Context triple: [Chef d’état-major de l’Armée de terre, instanceOf, French military position]
-
A.
French Army formation
A French Army formation is an organized military unit or grouping within the French Army, structured and equipped to conduct specific operational, tactical, or administrative functions.
-
B.
French military leader
chosen
A French military leader is a high-ranking officer from France responsible for planning, directing, and commanding military operations and forces in defense of national interests.
-
C.
French Revolutionary army
The French Revolutionary army was the mass conscripted military force of revolutionary France that combined ideological zeal, innovative organization, and large citizen armies to defend and spread the Revolution across Europe.
-
D.
Polish military position
A Polish military position is an organized role or rank within Poland's armed forces, defined by specific duties, authority, and responsibilities in the national defense structure.
-
E.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.