Triple
T27572982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Train Advise Assist Command – North |
E696081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military advisory command |
C52940
|
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: military advisory command Context triple: [Train Advise Assist Command – North, instanceOf, military advisory command]
-
A.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. Armed Forces.
-
B.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
C.
military aviation command
A military aviation command is an organizational unit responsible for planning, directing, coordinating, and controlling the employment, readiness, and support of air forces to achieve strategic and operational military objectives.
-
D.
military police command
A military police command is an organizational unit within the armed forces responsible for law enforcement, security operations, discipline, and order among military personnel and installations.
-
E.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:44 p.m.