Triple

T1911705
Position Surface form Disambiguated ID Type / Status
Subject Intermediate-Range Nuclear Forces Treaty E38123 entity
Predicate legalBasisForWithdrawal P20299 FINISHED
Object Article XV 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: Article XV | Statement: [Intermediate-Range Nuclear Forces Treaty, legalBasisForWithdrawal, Article XV]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalBasisForWithdrawal
Context triple: [Intermediate-Range Nuclear Forces Treaty, legalBasisForWithdrawal, Article XV]
  • A. legalBasis
    Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
  • B. hasWithdrawalClause chosen
    Indicates that an agreement or contract includes a provision specifying how a party may withdraw or terminate their participation.
  • C. reasonForWithdrawal
    Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
  • D. legalBasisWeakenedBy
    Indicates that the legal force, validity, or effectiveness of something is reduced or undermined by another factor, action, or decision.
  • E. basedOnAgreementWith
    Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
  • 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_69a8862a26088190aae5243695aeefc0 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb34d94fc8190a5bf1e582c77c725 completed March 7, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69abafeba3d88190afcce67483d8625b completed March 7, 2026, 4:56 a.m.
Created at: March 4, 2026, 7:35 p.m.