Triple
T32520104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MILMED COE |
E831156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO Centre of Excellence |
C61546
|
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 Centre of Excellence Context triple: [MILMED COE, instanceOf, NATO Centre of Excellence]
-
A.
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.
-
B.
NATO maritime headquarters
A NATO maritime headquarters is a command-and-control organization responsible for planning, coordinating, and directing multinational naval operations and maritime security activities within an assigned area or mission.
-
C.
NATO committee
chosen
A NATO committee is a formal group within the North Atlantic Treaty Organization composed of representatives from member states, tasked with discussing, coordinating, and making recommendations on specific policy, military, or administrative issues.
-
D.
European Union military headquarters
A European Union military headquarters is a central command facility responsible for planning, coordinating, and directing the EU’s joint military operations and defense activities across member states.
-
E.
U.S. Army center of excellence
A U.S. Army center of excellence is an institutional organization that develops, integrates, and advances specialized doctrine, training, capabilities, and expertise for a specific warfighting or functional area across the Army.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.