Triple
T23055771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 38th Troop Command |
E574151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | command-level headquarters |
C12848
|
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: command-level headquarters Context triple: [38th Troop Command, instanceOf, command-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.
major command echelon
chosen
A major command echelon is a high-level organizational tier within a military or large institution that oversees multiple subordinate units and directs strategic operations, resources, and policies across a broad mission area.
-
C.
high-readiness headquarters
A high-readiness headquarters is a command center designed, staffed, and equipped to rapidly assume control of operations, coordinate resources, and make timely decisions in response to emerging crises or missions.
-
D.
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.
-
E.
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.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:55 p.m.