Triple
T32734098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buenos Aires regional bureau |
E837028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | INTERPOL regional bureau |
C27359
|
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 regional bureau Context triple: [Buenos Aires regional bureau, instanceOf, INTERPOL regional bureau]
-
A.
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.
-
B.
international police cooperation office
chosen
An international police cooperation office is an organizational unit that coordinates information exchange, joint operations, and mutual legal assistance between law enforcement agencies of different countries to combat transnational crime.
-
C.
organ of Europol
An organ of Europol is an official institutional body within the European Union Agency for Law Enforcement Cooperation that performs specific governance, oversight, advisory, or operational functions in support of Europol’s mandate.
-
D.
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.
-
E.
Europol system
The Europol system is an integrated information and coordination platform that supports European law enforcement agencies in sharing intelligence, analyzing criminal data, and coordinating cross-border investigations.
- 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.