Triple
T21801644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interpol National Central Bureau in Japan |
E538251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement liaison office |
C39562
|
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: law enforcement liaison office Context triple: [Interpol National Central Bureau in Japan, instanceOf, law enforcement liaison office]
-
A.
law enforcement office
chosen
A law enforcement office is a physical workplace where police or other authorized agencies coordinate, manage, and support activities related to maintaining public safety and enforcing laws.
-
B.
government liaison office
A government liaison office is an organizational unit that facilitates communication, coordination, and collaboration between a government entity and external stakeholders such as other agencies, businesses, or the public.
-
C.
law enforcement unit
A law enforcement unit is an organized group within a policing or security agency tasked with enforcing laws, maintaining public order, and conducting specialized operations or investigations.
-
D.
law enforcement agency network
A law enforcement agency network is an interconnected system of local, regional, and national policing and investigative bodies that share information, resources, and coordination mechanisms to prevent, detect, and respond to crime and public safety threats.
-
E.
law enforcement body
A law enforcement body is an organized governmental agency responsible for maintaining public order, preventing and investigating crime, and enforcing laws within a defined jurisdiction.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.