Triple

T16269885
Position Surface form Disambiguated ID Type / Status
Subject High Contracting Parties E394970 entity
Predicate acquireStatusBy P38040 FINISHED
Object ratification of a treaty 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: ratification of a treaty | Statement: [High Contracting Parties, acquireStatusBy, ratification of a treaty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: acquireStatusBy
Context triple: [High Contracting Parties, acquireStatusBy, ratification of a treaty]
  • A. obtainedStatus chosen
    Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
  • B. acquisitionStatus
    Indicates the current state or outcome of an acquisition process between entities (e.g., pending, completed, failed, or canceled).
  • C. seeksStatusAs
    Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
  • D. classStatus
    Indicates the current academic or enrollment standing of an entity within a class or course context.
  • E. coordinateStatus
    Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
  • 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_69d87f221d8081909b0b2063e7528ba2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24608dd20819082f46a64af233038 completed April 17, 2026, 2:39 p.m.
PD Predicate disambiguation batch_69e219f259e88190bf49d8408c04178e completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:05 a.m.