Triple
T3932328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French I Corps |
E90822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French Army formation |
C14617
|
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 Army formation Context triple: [French I Corps, instanceOf, French Army formation]
-
A.
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.
-
B.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
C.
United States Army formation type
A United States Army formation type is a standardized organizational structure that defines the size, composition, and command hierarchy of Army units for specific operational roles and missions.
-
D.
military personnel of the French Revolutionary Wars
Individuals who served in the armed forces of France or opposing states during the French Revolutionary Wars (1792–1802), participating in military operations, command, support, or related roles.
-
E.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
- F. None of above. chosen
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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.