Triple
T5739398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Defence Services Examination |
E126576
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence services recruitment examination |
C13301
|
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: defence services recruitment examination Context triple: [Combined Defence Services Examination, instanceOf, defence services recruitment examination]
-
A.
All India Service
All India Service is a category of elite civil services in India whose officers are recruited centrally but serve under both the central and state governments, holding key administrative, policing, and forestry positions across the country.
-
B.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
C.
defense minister
A defense minister is a high-ranking government official responsible for formulating and overseeing a nation's defense policy, military strategy, and armed forces administration.
-
D.
military selection course
chosen
A military selection course is an intensive, highly structured program designed to evaluate and filter candidates for specialized military roles through rigorous physical, mental, and psychological challenges.
-
E.
defence staff committee
A defence staff committee is a formal group of senior military and defence officials convened to coordinate policy, planning, and strategic decision-making for national or organizational security.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:48 p.m.