Triple

T27524046
Position Surface form Disambiguated ID Type / Status
Subject Japan–South Korea E694786 entity
Predicate hasSecurityAgreement P38198 FINISHED
Object General Security of Military Information Agreement 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: General Security of Military Information Agreement | Statement: [Japan–South Korea, hasSecurityAgreement, General Security of Military Information Agreement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecurityAgreement
Context triple: [Japan–South Korea, hasSecurityAgreement, General Security of Military Information Agreement]
  • A. hasSecurityClause
    Indicates that an agreement, contract, or document includes a provision specifying security-related requirements, protections, or safeguards.
  • B. hasAgreementSystem
    Indicates that there exists a specific grammatical agreement system (e.g., for features like number, gender, or person) associated with the given entity.
  • C. hasTypeOfAgreement chosen
    Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
  • D. hasCustomerAgreement
    Indicates that a customer is bound by or associated with a specific agreement or contract.
  • E. hasSecurityRelationship
    Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
  • 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_69ef538550208190aa9de8e2cb260d93 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69fce28d6c3081908bf76f5db63ecf68 completed May 7, 2026, 7:05 p.m.
PD Predicate disambiguation batch_69fce12d2f08819082134b5eb3db6a24 completed May 7, 2026, 6:59 p.m.
Created at: April 27, 2026, 1:22 p.m.