Triple
T33813901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Inspector Japp |
E866615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scotland Yard officer |
C20492
|
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: Scotland Yard officer Context triple: [Chief Inspector Japp, instanceOf, Scotland Yard officer]
-
A.
British police officer
chosen
A British police officer is a sworn law enforcement official in the United Kingdom responsible for maintaining public order, preventing and investigating crime, and protecting the public in accordance with UK law and policing standards.
-
B.
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.
-
C.
British magistrate
A British magistrate is a judicial officer, often a trained volunteer, who presides over lower courts to hear minor criminal cases, some civil matters, and preliminary hearings, applying the law and determining appropriate outcomes within limited sentencing powers.
-
D.
Brunswick officer
A Brunswick officer is a military leader from the historical Duchy of Brunswick, responsible for commanding troops, enforcing discipline, and executing the strategic and tactical directives of the Brunswick armed forces.
-
E.
member of the Ankh-Morpork City Watch
A member of the Ankh-Morpork City Watch is a often-overworked, underpaid, and frequently eccentric law enforcer tasked with maintaining a semblance of order in the chaotic, multi-species metropolis of Ankh-Morpork.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.