Triple

T18874909
Position Surface form Disambiguated ID Type / Status
Subject Contracting Parties to the 1998 Agreement E461656 entity
Predicate canWithdrawFrom P133292 FINISHED
Object 1998 Agreement under its withdrawal provisions 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: 1998 Agreement under its withdrawal provisions | Statement: [Contracting Parties to the 1998 Agreement, canWithdrawFrom, 1998 Agreement under its withdrawal provisions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canWithdrawFrom
Context triple: [Contracting Parties to the 1998 Agreement, canWithdrawFrom, 1998 Agreement under its withdrawal provisions]
  • A. canWithdraw
    Indicates that an entity has the permission or ability to withdraw something (such as funds, items, or resources) from a source or account.
  • B. mayWithdrawBy
    Indicates that an entity is permitted to perform a withdrawal using a specified method, channel, or instrument.
  • C. canWithdrawConfidenceFrom
    Indicates that an entity has the authority or ability to revoke or remove its previously given confidence or support from another entity.
  • D. withdrawalType
    Indicates the specific method or category by which a withdrawal is carried out in a given context.
  • E. withdrewFrom
    Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
  • 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_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.
PDg Predicate description generation batch_69e49785fd7081909577e90a55df0a35 completed April 19, 2026, 8:51 a.m.
Created at: April 10, 2026, 11:57 a.m.