Triple
T28480840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Medical Publications |
E720684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military medical doctrine |
C54111
|
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 doctrine Context triple: [Allied Medical Publications, instanceOf, military medical doctrine]
-
A.
military organizational doctrine
Military organizational doctrine is the formalized set of principles, structures, and procedures that guide how armed forces are organized, coordinated, and employed to achieve strategic and operational objectives.
-
B.
military training doctrine
A military training doctrine is a formalized set of principles, methods, and standards that guides how armed forces prepare personnel and units to plan, fight, and support operations effectively and consistently.
-
C.
military doctrinal framework
A military doctrinal framework is a structured set of principles, concepts, and guidelines that shapes how armed forces plan, organize, and conduct operations across different levels of war.
-
D.
military doctrine handbook
A military doctrine handbook is an authoritative manual that outlines the fundamental principles, strategies, tactics, and procedures guiding the planning and conduct of military operations.
-
E.
military medical institution
A military medical institution is an organization within the armed forces that provides healthcare, medical training, and research services to military personnel, their families, and sometimes civilians, often in support of operational readiness and defense missions.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:55 a.m.