Triple
T3477988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st CEB |
E73420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Marine Corps combat engineer battalion |
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 Marine Corps combat engineer battalion Context triple: [1st CEB, instanceOf, United States Marine Corps combat engineer battalion]
-
A.
regiment of the United States Marine Corps
A regiment of the United States Marine Corps is a mid-level, combat-capable organizational unit typically composed of several battalions, providing command, control, and support for large-scale Marine operations.
-
B.
U.S. Army aviation brigade
A U.S. Army aviation brigade is a large, modular combat unit that provides coordinated helicopter and unmanned aircraft support for assault, reconnaissance, transport, and logistical missions in support of ground forces.
-
C.
component of the United States Marine Corps
A component of the United States Marine Corps is a distinct organizational element, such as a command, unit, or supporting establishment, that contributes specific capabilities and functions to the Corps’ overall mission.
-
D.
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.
-
E.
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.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.