Triple
T12872475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hôpital d'instruction des armées Bégin |
E307883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hospital of the French Armed Forces Health Service |
C15201
|
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: hospital of the French Armed Forces Health Service Context triple: [Hôpital d'instruction des armées Bégin, instanceOf, hospital of the French Armed Forces Health Service]
-
A.
branch of the French Armed Forces
A branch of the French Armed Forces is a major organizational component, such as the Army, Navy, Air and Space Force, or Gendarmerie, responsible for specific military roles, capabilities, and operations under national defense policy.
-
B.
military medical branch
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.
-
C.
French military personnel
Individuals who serve or have served in the armed forces of France, including the Army, Navy, Air and Space Force, National Gendarmerie, and related military branches.
-
D.
hospital system facilities
chosen
A hospital system facilities class represents the physical infrastructure, equipment, and support services that enable the delivery of healthcare across one or more hospital locations.
-
E.
U.S. Army medical unit
A U.S. Army medical unit is a military organization that provides coordinated medical care, treatment, evacuation, and health support to soldiers and authorized personnel in both garrison and deployed operational environments.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:38 p.m.