Triple
T29423168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11 Medical Company |
E746209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unit of the Royal Netherlands Army |
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: unit of the Royal Netherlands Army Context triple: [11 Medical Company, instanceOf, unit of the Royal Netherlands Army]
-
A.
branch of the Royal Netherlands Navy
A branch of the Royal Netherlands Navy is a distinct organizational component responsible for specific maritime defense, support, or operational functions within the overall naval structure of the Netherlands.
-
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.
Belgian Air Force unit
A Belgian Air Force unit is an organizational subdivision of the Belgian Air Component, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support missions within national and allied defense frameworks.
-
D.
Belgian Air Force unit
A Belgian Air Force unit is an organizational entity within the Belgian Air Component responsible for executing specific air defense, support, training, or operational missions using assigned personnel, aircraft, and equipment.
-
E.
Belgian military institution
A Belgian military institution is an organization within Belgium’s defense structure responsible for training, organizing, and supporting the country’s armed forces in accordance with national and international 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:07 p.m.