Triple

T23620936
Position Surface form Disambiguated ID Type / Status
Subject Japan–Soviet Joint Declaration of 1956 E583315 entity
Predicate linkedDispute P26178 FINISHED
Object Kuril Islands dispute 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: Kuril Islands dispute | Statement: [Japan–Soviet Joint Declaration of 1956, linkedDispute, Kuril Islands dispute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: linkedDispute
Context triple: [Japan–Soviet Joint Declaration of 1956, linkedDispute, Kuril Islands dispute]
  • A. laterDisputedBy
    Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
  • B. hasDisputeWith
    Indicates that there is a conflict, disagreement, or contested issue between two entities.
  • C. disputeInvolves chosen
    Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
  • D. statusDisputedBy
    Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
  • E. disputeResolvedBy
    Indicates that a particular dispute or conflict has been settled or resolved through the actions, decision, or intervention of a specified party or process.
  • 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_69e248fbcd9081908ba08913f9d30826 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b178d20c819094b547c6c7ae6c01 completed April 29, 2026, 7:21 a.m.
PD Predicate disambiguation batch_69f118d0e0588190a86527a7747c5427 completed April 28, 2026, 8:30 p.m.
Created at: April 17, 2026, 6:45 p.m.