Triple

T23973414
Position Surface form Disambiguated ID Type / Status
Subject START II E604296 entity
Predicate entryIntoForceRequirement P12709 FINISHED
Object exchange of instruments of ratification 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: exchange of instruments of ratification | Statement: [START II, entryIntoForceRequirement, exchange of instruments of ratification]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: entryIntoForceRequirement
Context triple: [START II, entryIntoForceRequirement, exchange of instruments of ratification]
  • A. enteredIntoForceBy chosen
    Indicates that a legal instrument, agreement, or provision became legally effective as a result of an action taken by a specified authority, event, or instrument.
  • B. enteredIntoForceIn
    Indicates that an agreement, law, or treaty became legally effective or operative in a specified place or jurisdiction.
  • C. hasEntryRequirement
    Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
  • D. enteredIntoForce
    Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
  • E. establishedRequirement
    Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
  • 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_69e29543019c8190872462e593cc50b4 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d1dda91c8190af716bceb3225aee completed April 29, 2026, 9:39 a.m.
PD Predicate disambiguation batch_69f161578d54819084a8b35496299993 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:25 p.m.