Triple
T17635014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African Intelligence Corps |
E430071
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the South African Army |
C39464
|
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: branch of the South African Army Context triple: [South African Intelligence Corps, instanceOf, branch of the South African Army]
-
A.
Air Force of Zimbabwe unit
An Air Force of Zimbabwe unit is an organizational subdivision of the Air Force of Zimbabwe, comprising personnel, aircraft, and equipment structured to perform specific operational, support, or training functions within the national air defense framework.
-
B.
branch of the Indian Army
A branch of the Indian Army is a major organizational subdivision responsible for specific operational, combat, or support functions within the Army’s overall structure.
-
C.
South African Air Force base
A South African Air Force base is a military installation that supports the South African Air Force’s operational, training, logistical, and administrative activities, including the housing, maintenance, and deployment of aircraft and personnel.
-
D.
branch of the Bundeswehr
A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
-
E.
branch of the Pakistan Army
A branch of the Pakistan Army is a major organizational subdivision responsible for specialized military functions, capabilities, and operations within the overall land warfare structure of Pakistan’s 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:52 a.m.