Triple
T3100947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staff and Personnel Support Branch |
E64716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military administrative corps |
C13719
|
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 administrative corps Context triple: [Staff and Personnel Support Branch, instanceOf, military administrative corps]
-
A.
military office
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support military operations.
-
B.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
C.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
-
D.
military system
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
-
E.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:03 p.m.