Triple
T7066163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Communications Unit |
E164356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States military unit |
C2497
|
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: United States military unit Context triple: [Joint Communications Unit, instanceOf, United States military unit]
-
A.
United States military formation
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.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
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.
-
D.
component of the United States Army
A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
-
E.
United States Marine Corps special operations unit
A United States Marine Corps special operations unit is an elite, highly trained Marine formation organized, equipped, and employed to conduct specialized missions such as direct action, special reconnaissance, and foreign internal defense in support of national security 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:39 p.m.