Triple
T32788200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INTERPOL Blue Notice |
E838554
|
entity |
| Predicate | informationTypeRequested |
P66881
|
FINISHED |
| Object | identity details |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: identity details | Statement: [INTERPOL Blue Notice, informationTypeRequested, identity details]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationTypeRequested Context triple: [INTERPOL Blue Notice, informationTypeRequested, identity details]
-
A.
informationTypeHandled
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
-
B.
typeOfInformation
chosen
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
C.
requiredInformation
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
D.
requestType
Indicates the specific kind or category of request being made in an interaction or transaction.
-
E.
informationCarrierType
Indicates the medium or format through which information is physically or digitally carried or delivered.
- F. None of above.
Provenance (3 batches)
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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.