Triple
T30250668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bylandt’s Brigade |
E769191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch-Belgian military unit |
C57183
|
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: Dutch-Belgian military unit Context triple: [Bylandt’s Brigade, instanceOf, Dutch-Belgian military unit]
-
A.
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.
-
B.
Belgian military personnel
Belgian military personnel are individuals who serve in Belgium’s armed forces, including the Land, Air, Naval, and Medical components, responsible for national defense, international missions, and support to civil authorities.
-
C.
corps of the Royal Netherlands Army
The corps of the Royal Netherlands Army is a major organizational and operational subdivision responsible for commanding and coordinating multiple brigades and support units within the Dutch land forces.
-
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 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.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:40 p.m.