Triple

T25338023
Position Surface form Disambiguated ID Type / Status
Subject Russia and Japan E635328 entity
Predicate shareMaritimeBoundary P39564 FINISHED
Object Sea of Japan 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: Sea of Japan | Statement: [Russia and Japan, shareMaritimeBoundary, Sea of Japan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareMaritimeBoundary
Context triple: [Russia and Japan, shareMaritimeBoundary, Sea of Japan]
  • A. sharesMaritimeBorders chosen
    Indicates that two entities have adjacent territorial waters or maritime zones that touch or overlap, forming a shared sea boundary.
  • B. maritimeBoundarySettledBy
    Indicates that the maritime boundary between two entities has been formally determined and agreed upon through a specific decision, treaty, or authoritative process.
  • C. maritimeBoundaryLengthApproxKm
    Indicates the approximate length, measured in kilometers, of a state's maritime boundary or coastline.
  • D. bordersStateAcrossSea
    Indicates that one state is separated from another by a sea but still directly borders it across that body of water.
  • E. separatesTerritorialWatersOf
    Indicates that one entity (typically a body of water or boundary) serves as a dividing line between the territorial waters of two or more distinct entities.
  • 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_69e75a99bd6481909476115b35b9a8e4 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f6e6029a10819098ff21f58079e70e completed May 3, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69f6e3d5e8188190b1e1c2e5d1b77031 completed May 3, 2026, 5:57 a.m.
Created at: April 21, 2026, 1:32 p.m.