Triple
T2002889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medical Service (Belgian Armed Forces) |
E43510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military medical service |
C2423
|
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: military medical service Context triple: [Medical Service (Belgian Armed Forces), instanceOf, military medical service]
-
A.
military medical branch
chosen
A military medical branch is the specialized division of a nation's armed forces responsible for providing healthcare, medical support, and emergency treatment to military personnel in both peacetime and combat operations.
-
B.
military community
A military community is a social group composed of service members, their families, veterans, and supporting personnel who share common experiences, resources, and culture related to military life.
-
C.
military-adjacent uniformed service
A military-adjacent uniformed service is an organized, government-sanctioned body whose members wear standardized uniforms and perform defense-, security-, or support-related functions alongside or in coordination with the armed forces, but are not formally part of the military.
-
D.
medical contingent
A medical contingent is a group of healthcare professionals and support staff organized to provide medical services and emergency care in a specific location, event, or operational context.
-
E.
military personnel category
A military personnel category is a classification that groups service members based on roles, ranks, duties, or service status within the armed forces.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.