Triple

T37140333
Position Surface form Disambiguated ID Type / Status
Subject CFAY E920086 entity
Predicate bilateralAgreementFramework P43350 FINISHED
Object U.S.-Japan Security Treaty NE NERFINISHED

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: U.S.-Japan Security Treaty | Statement: [CFAY, bilateralAgreementFramework, U.S.-Japan Security Treaty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bilateralAgreementFramework
Context triple: [CFAY, bilateralAgreementFramework, U.S.-Japan Security Treaty]
  • A. hasCooperationFramework chosen
    Indicates that two or more entities are formally linked by an agreed framework that governs how they cooperate or collaborate with each other.
  • B. internationalAgreementBasis
    Indicates that one entity serves as the legal or formal basis for an international agreement involving another entity.
  • C. bilateralRelation
    Indicates a mutual or two-way relationship between two entities, where each affects or interacts with the other.
  • D. coordinatesBilateralRelationsBetween
    Indicates that one entity organizes, manages, or facilitates the diplomatic or cooperative relationship between two other entities.
  • E. establishedMutualDefenseCommitment
    Indicates that two or more parties have formally agreed to defend and support each other if any one of them is attacked or threatened.
  • 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_69f76e9e9d008190a250b0387c992c74 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb344c60f8819090f2e21e1e61d621 completed May 6, 2026, 12:30 p.m.
PD Predicate disambiguation batch_69fb2f642db08190b562725502c74ea6 completed May 6, 2026, 12:09 p.m.
Created at: May 3, 2026, 4:15 p.m.