Triple
T32734369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INTERPOL Diffusion |
E837035
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | INTERPOL alert mechanism |
C25194
|
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: INTERPOL alert mechanism Context triple: [INTERPOL Diffusion, instanceOf, INTERPOL alert mechanism]
-
A.
INTERPOL regulatory instrument
An INTERPOL regulatory instrument is an official framework of rules, procedures, or guidelines adopted by INTERPOL to govern international police cooperation, information exchange, and operational activities among its member countries.
-
B.
Interpol notice
chosen
An Interpol notice is an international alert issued by Interpol to share critical police information across member countries for purposes such as locating, arresting, or obtaining information about persons or threats.
-
C.
international police alert
An international police alert is a formal notification issued by law enforcement agencies across national borders to share critical information about suspects, crimes, or security threats and to request cooperation from foreign authorities.
-
D.
Interpol liaison office
An Interpol liaison office is a specialized unit that facilitates communication, coordination, and information exchange between national law enforcement agencies and Interpol’s international policing network.
-
E.
AMBER Alert program
The AMBER Alert program is a coordinated emergency response system that rapidly disseminates information about abducted children to the public through media and communication networks to aid in their safe recovery.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.