Triple
T762928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Southern Command |
E16110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographic combatant command |
C4235
|
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: geographic combatant command Context triple: [U.S. Southern Command, instanceOf, geographic combatant command]
-
A.
United States Army major command
A United States Army major command is a high-level organizational entity responsible for overseeing and directing large-scale Army operations, resources, and support functions within a specific mission area or geographic region.
-
B.
military campaign theater
A military campaign theater is a geographically defined area where coordinated military operations and strategies are conducted to achieve specific objectives within a broader conflict.
-
C.
theatre command
chosen
Theatre command is a high-level military headquarters responsible for planning, directing, and coordinating operations across a broad geographic area or theater of war.
-
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 Marine Corps major command
A United States Marine Corps major command is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale Marine Corps forces and operations within a defined functional or geographic area.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.