Triple
T24781124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korsakovsky District, Sakhalin Oblast |
E619997
|
entity |
| Predicate | hasMaritimeBorderProximityTo |
P212
|
FINISHED |
| Object | 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: Japan | Statement: [Korsakovsky District, Sakhalin Oblast, hasMaritimeBorderProximityTo, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeBorderProximityTo Context triple: [Korsakovsky District, Sakhalin Oblast, hasMaritimeBorderProximityTo, Japan]
-
A.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
B.
neighboringCountryBySea
Indicates that one country is adjacent to another with their territories touching via a shared sea boundary rather than solely by land.
-
C.
hasCoastlineOn
chosen
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
-
D.
maritimeBoundaryLengthApproxKm
Indicates the approximate length, measured in kilometers, of a state's maritime boundary or coastline.
-
E.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 4:44 a.m.