Triple
T16605773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Army engineering corps |
E403444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the French Army |
C24971
|
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: branch of the French Army Context triple: [French Army engineering corps, instanceOf, branch of the French Army]
-
A.
branch of the French Armed Forces
chosen
A branch of the French Armed Forces is a major organizational component, such as the Army, Navy, Air and Space Force, or Gendarmerie, responsible for specific military roles, capabilities, and operations under national defense policy.
-
B.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
C.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
D.
branch of the Bundeswehr
A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
-
E.
French military personnel
Individuals who serve or have served in the armed forces of France, including the Army, Navy, Air and Space Force, National Gendarmerie, and related military branches.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.