Triple
T35713802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNBG-W |
E1031941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | KFOR maneuver unit |
C62260
|
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: KFOR maneuver unit Context triple: [MNBG-W, instanceOf, KFOR maneuver unit]
-
A.
KFOR base
A KFOR base is a military installation used by NATO-led Kosovo Force troops as a secure hub for operations, logistics, and coordination in maintaining peace and stability in Kosovo.
-
B.
Maneuver Enhancement Brigade
A Maneuver Enhancement Brigade is a modular U.S. Army support formation designed to enhance the freedom of movement, protection, and sustainment of combat forces by integrating engineer, military police, CBRN, and other enabling capabilities.
-
C.
Marine Air-Ground Task Force logistics element
The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
-
D.
Special Purpose Marine Air-Ground Task Force
A Special Purpose Marine Air-Ground Task Force is a scalable, rapidly deployable, task-organized Marine Corps force combining ground, aviation, and logistics elements tailored to accomplish specific missions.
-
E.
Oklahoma Army National Guard unit
An Oklahoma Army National Guard unit is a state-based military organization composed of citizen-soldiers who train part-time to provide combat, support, and emergency response capabilities for both state and federal missions.
- F. None of above. chosen
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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.