Triple
T23489741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Service Commission |
E570636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | officer entry scheme |
C47743
|
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: officer entry scheme Context triple: [Short Service Commission, instanceOf, officer entry scheme]
-
A.
police officer
A police officer is a law enforcement professional responsible for maintaining public order, preventing and investigating crimes, and protecting the safety and rights of individuals within a community.
-
B.
occupation authority component
An occupation authority component is a system element responsible for defining, managing, and enforcing rules, permissions, and responsibilities associated with specific roles or professions within an organizational or regulatory context.
-
C.
SS officer
An SS officer is a member of the Schutzstaffel, the paramilitary organization of Nazi Germany responsible for enforcing Nazi ideology, overseeing concentration and extermination camps, and perpetrating widespread war crimes and crimes against humanity during World War II.
-
D.
occupation authority office
An occupation authority office is an administrative body established by a foreign power to govern, regulate, and oversee civil, legal, and economic affairs in a territory under military or political occupation.
-
E.
occupation authority section
An occupation authority section is a designated part of a document or system that defines, records, and manages the official powers, responsibilities, and permissions associated with a specific job or role.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:04 p.m.