Triple
T18313083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Expeditionary Force in Burma |
E438679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese military formation |
C19405
|
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: Chinese military formation Context triple: [Chinese Expeditionary Force in Burma, instanceOf, Chinese military formation]
-
A.
army formation
chosen
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
B.
military parade
A military parade is a formal, organized procession of armed forces showcasing personnel, equipment, discipline, and national power, often held for ceremonial or commemorative purposes.
-
C.
military formation collection
A military formation collection is an organized set of multiple military units or formations grouped together for coordinated command, maneuver, and operational effectiveness.
-
D.
Russian military formation
A Russian military formation is an organized grouping of Russian armed forces personnel and equipment, structured at various hierarchical levels (such as squad, platoon, company, battalion, regiment, brigade, division, or army) to conduct coordinated combat and support operations.
-
E.
militia-style military formation
A militia-style military formation is an organized group of primarily non-professional, part-time fighters drawn from the civilian population, structured for local defense or irregular warfare under limited formal military hierarchy and training.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.