Triple
T4002133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyber and Information Domain Service |
E89437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | service branch of the Bundeswehr |
C15123
|
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: service branch of the Bundeswehr Context triple: [Cyber and Information Domain Service, instanceOf, service branch of the Bundeswehr]
-
A.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
B.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
C.
branch of the United States Armed Forces
A branch of the United States Armed Forces is a distinct military service component (such as the Army, Navy, Air Force, Marine Corps, Space Force, or Coast Guard) with its own mission, structure, and responsibilities for national defense and security.
-
D.
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.
-
E.
military support organization
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:34 p.m.