Triple

T27172808
Position Surface form Disambiguated ID Type / Status
Subject Interpol Red Notice list E682964 entity
Predicate relatedTo P37 FINISHED
Object Interpol Yellow Notice
An Interpol Yellow Notice is an international police alert used to help locate missing persons, often minors, or to identify persons who are unable to identify themselves.
E1760285 NE 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: Interpol Yellow Notice | Statement: [Interpol Red Notice list, relatedTo, Interpol Yellow Notice]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Interpol Yellow Notice
Triple: [Interpol Red Notice list, relatedTo, Interpol Yellow Notice]
Generated description
An Interpol Yellow Notice is an international police alert used to help locate missing persons, often minors, or to identify persons who are unable to identify themselves.

Provenance (5 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_69eefad086808190ab89816c0c300476 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f62549039c8190af7159d07416c985 completed May 2, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a125388d6a0819092971a404f7992c5 completed May 24, 2026, 1:25 a.m.
NEDg Description generation batch_6a12546f814881908c806a1805b7473d completed May 24, 2026, 1:29 a.m.
NED2 Entity disambiguation (via description) batch_6a125512eb608190b958f82af3475535 completed May 24, 2026, 1:32 a.m.
Created at: April 27, 2026, 9:24 a.m.