Triple
T30122295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO operational support units |
E765591
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO force element |
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: NATO force element Context triple: [NATO operational support units, instanceOf, NATO force element]
-
A.
NATO personnel
NATO personnel are individuals serving in military, civilian, or support roles within the North Atlantic Treaty Organization, responsible for implementing its collective defense, crisis management, and cooperative security missions.
-
B.
multinational airborne army formation
A multinational airborne army formation is a coordinated military unit composed of airborne-capable forces from multiple nations, trained and organized to conduct joint air-delivered operations under a unified command structure.
-
C.
NATO rapid reaction corps headquarters
The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
-
D.
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.
-
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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:13 p.m.