Triple
T23489240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commandant, Central Reserve Police Force |
E570624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior field-level rank |
C3908
|
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: senior field-level rank Context triple: [Commandant, Central Reserve Police Force, instanceOf, senior field-level rank]
-
A.
senior enlisted rank
chosen
A senior enlisted rank is a high-level non-commissioned position in the military hierarchy, typically responsible for expert technical skills, leadership, and advising officers on enlisted matters.
-
B.
senior clerical rank
A senior clerical rank is a high-level position within a religious or administrative hierarchy, typically involving significant authority, oversight responsibilities, and decision-making power over lower-ranking clerical roles.
-
C.
military-equivalent rank
A military-equivalent rank is a formal position or title in a non-military organization that is defined to correspond in status, authority, or protocol to a specific rank within a military hierarchy.
-
D.
senior naval command position
A senior naval command position is a high-ranking leadership role responsible for directing major naval units or formations, making strategic and operational decisions, and ensuring the effective readiness and employment of maritime forces.
-
E.
senior military advisory position
A senior military advisory position is a high-ranking role responsible for providing expert strategic, operational, and policy guidance to top government or defense leaders to inform national security decisions.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:04 p.m.