Triple

T18874907
Position Surface form Disambiguated ID Type / Status
Subject Contracting Parties to the 1998 Agreement E461656 entity
Predicate mustNotify P41194 FINISHED
Object accession to the UN Secretary-General 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: accession to the UN Secretary-General | Statement: [Contracting Parties to the 1998 Agreement, mustNotify, accession to the UN Secretary-General]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mustNotify
Context triple: [Contracting Parties to the 1998 Agreement, mustNotify, accession to the UN Secretary-General]
  • A. requiresNotification chosen
    Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
  • B. requiresNotificationTo
    Indicates that one entity must send a notification to another entity before or when a certain condition, event, or action occurs.
  • C. requiresNotificationFrom
    Indicates that one entity must receive a notification from another entity before or when a certain condition, event, or action occurs.
  • D. mustTell
    Indicates that one entity is obligated or required to inform or disclose something to another entity.
  • E. mustTouch
    Indicates that the entities are required to be in direct physical contact with each other.
  • 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c3cd49748190948d535918aec3de completed April 20, 2026, 6:12 a.m.
PD Predicate disambiguation batch_69e48d22dde8819093b1d963bd673365 completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:57 a.m.