Triple

T10054767
Position Surface form Disambiguated ID Type / Status
Subject Interpol General Assembly E208832 entity
Predicate meetsForPurpose P91851 FINISHED
Object to set Interpol policies 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: to set Interpol policies | Statement: [Interpol General Assembly, meetsForPurpose, to set Interpol policies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: meetsForPurpose
Context triple: [Interpol General Assembly, meetsForPurpose, to set Interpol policies]
  • A. meets
    Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
  • B. meetsTo
    Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
  • C. meetsAs
    Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
  • D. meetsUnder
    Indicates that one entity encounters or comes together with another entity in a context where it is subordinate to, governed by, or occurring within the scope or authority of a third entity or condition.
  • E. meetsBetween
    Indicates that one entity meets or encounters another at some point between two specified reference points or times.
  • F. None of above. chosen

Provenance (4 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_69ca836094408190a36a1ea7e9a86fcd completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cdcfab39408190ac728fe156eed658 completed April 2, 2026, 2:08 a.m.
PD Predicate disambiguation batch_69cd4b8d2280819089de27e57babd1f3 completed April 1, 2026, 4:45 p.m.
PDg Predicate description generation batch_69cd4f8d9b888190b8067bd916dae773 completed April 1, 2026, 5:02 p.m.
Created at: March 30, 2026, 8:57 p.m.