Triple
T32403863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Corps (Forward) Japan |
E828024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corps-level headquarters |
C21793
|
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: corps-level headquarters Context triple: [I Corps (Forward) Japan, instanceOf, corps-level headquarters]
-
A.
deployable corps-level headquarters
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.
-
B.
corps artillery headquarters
chosen
A corps artillery headquarters is the command element responsible for planning, coordinating, and controlling all artillery and fire support operations within a military corps.
-
C.
headquarters and service regiment
A headquarters and service regiment is a military unit that provides command, control, and essential administrative and logistical support functions for a larger formation or group of subordinate units.
-
D.
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.
-
E.
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.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:53 a.m.