Triple

T36916017
Position Surface form Disambiguated ID Type / Status
Subject Russia–Japan relations E913046 entity
Predicate diplomaticMissionOfJapanInRussia P174994 FINISHED
Object Embassy of Japan in Moscow 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: Embassy of Japan in Moscow | Statement: [Russia–Japan relations, diplomaticMissionOfJapanInRussia, Embassy of Japan in Moscow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: diplomaticMissionOfJapanInRussia
Context triple: [Russia–Japan relations, diplomaticMissionOfJapanInRussia, Embassy of Japan in Moscow]
  • A. JapanDiplomaticRepresentation chosen
    Indicates the formal diplomatic relationship or representation that Japan maintains with another country or international entity.
  • B. embassyOfJapanLocation
    Indicates the location where the Embassy of Japan is situated or hosted.
  • C. headquartersDuringRussoJapaneseWar
    Indicates the location that served as an entity’s headquarters specifically during the Russo-Japanese War.
  • D. JapaneseMission
    Indicates a mission, delegation, or official undertaking that is specifically associated with Japan or originates from Japanese authorities or organizations.
  • E. ledLegationTo
    Indicates that one entity headed or directed a diplomatic mission or delegation to another entity or location.
  • 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_69f76e885b848190bad82c87e9525486 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb563aec448190875410fb1a3ed624 completed May 6, 2026, 2:54 p.m.
PD Predicate disambiguation batch_69fb35b9ede881908aaae93a215525df completed May 6, 2026, 12:36 p.m.
Created at: May 3, 2026, 4:13 p.m.