Triple
T4232027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Australian Army Medical Corps |
E94601
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | army medical corps |
C9667
|
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: army medical corps Context triple: [Royal Australian Army Medical Corps, instanceOf, army medical corps]
-
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 administrative corps
A military administrative corps is a specialized branch of the armed forces responsible for managing personnel, logistics, finance, records, and other support functions that enable effective military operations.
-
C.
army aviation corps
The army aviation corps is a military branch responsible for providing aerial support, reconnaissance, transport, and combat capabilities to ground forces using helicopters and other aircraft.
-
D.
United States Air Force medical unit
A United States Air Force medical unit is an organized group within the USAF responsible for providing medical care, aeromedical evacuation, and health support to Air Force personnel and operations in both peacetime and combat environments.
-
E.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:05 p.m.