Triple
T33410061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10th Group |
E855554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army Special Forces group |
C61189
|
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. Army Special Forces group Context triple: [10th Group, instanceOf, U.S. Army Special Forces group]
-
A.
U.S. Army Ranger unit
A U.S. Army Ranger unit is an elite, highly trained light infantry force specializing in rapid deployment, direct action raids, special reconnaissance, and other high-risk missions in support of U.S. military objectives.
-
B.
Marine Corps special operations unit
A Marine Corps special operations unit is an elite, highly trained military formation specializing in direct action, special reconnaissance, and unconventional warfare in maritime and littoral environments.
-
C.
Operational Detachment Alpha
Operational Detachment Alpha is a small, highly trained U.S. Army Special Forces team designed to conduct specialized missions such as unconventional warfare, foreign internal defense, and special reconnaissance, often operating independently in austere environments.
-
D.
special forces–type unit
chosen
A special forces–type unit is a highly trained, elite military or paramilitary team specialized in conducting high-risk, precision missions such as reconnaissance, counterterrorism, and unconventional warfare, often behind enemy lines or in politically sensitive environments.
-
E.
U.S. Army task force
A U.S. Army task force is a temporary, mission-tailored organization composed of units from different branches and echelons, formed to accomplish a specific operational objective.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.