Triple
T19588529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Corps (South Vietnam) |
E470167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | army corps-level command |
C25290
|
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: army corps-level command Context triple: [I Corps (South Vietnam), instanceOf, army corps-level command]
-
A.
field army–level command
A field army–level command is a large, operational military formation responsible for directing multiple corps or equivalent units within a theater of operations to achieve strategic objectives.
-
B.
deployable corps-level headquarters
chosen
A deployable corps-level headquarters is a mobile, command-and-control organization capable of planning, coordinating, and directing large-scale, multi-division military operations across a theater of operations.
-
C.
Major Command Subordinate Unit
A Major Command Subordinate Unit is an organizational entity that operates under a major command, executing its directives and managing assigned missions, resources, and personnel within a defined scope of responsibility.
-
D.
United States Army command
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
-
E.
United States Army field army
A United States Army field army is a large, operational-level formation typically composed of multiple corps, organized to conduct sustained, large-scale land combat operations within a theater of war.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.