Triple
T16936792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Marine Corps Forces, Central Command |
E410849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. military formation |
C9194
|
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: U.S. military formation Context triple: [U.S. Marine Corps Forces, Central Command, instanceOf, U.S. military formation]
-
A.
United States military formation
chosen
A United States military formation is an organized grouping of U.S. armed forces personnel and units, structured and deployed to conduct specific missions or operations under a defined command hierarchy.
-
B.
United States Army formation type
A United States Army formation type is a standardized organizational structure that defines the size, composition, and command hierarchy of Army units for specific operational roles and missions.
-
C.
U.S. Navy formation
A U.S. Navy formation is an organized arrangement of naval vessels or aircraft maneuvering together under a unified command to achieve tactical, operational, or ceremonial objectives at sea or in the air.
-
D.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
E.
branch of the United States Armed Forces
A branch of the United States Armed Forces is a distinct military service component (such as the Army, Navy, Air Force, Marine Corps, Space Force, or Coast Guard) with its own mission, structure, and responsibilities for national defense and security.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.