Triple
T24781087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korsakovsky District, Sakhalin Oblast |
E619997
|
entity |
| Predicate | locatedInTheSouthernPartOf |
P161618
|
FINISHED |
| Object | Sakhalin Island |
—
|
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: Sakhalin Island | Statement: [Korsakovsky District, Sakhalin Oblast, locatedInTheSouthernPartOf, Sakhalin Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheSouthernPartOf Context triple: [Korsakovsky District, Sakhalin Oblast, locatedInTheSouthernPartOf, Sakhalin Island]
-
A.
locatedInSouthwesternPartOf
Indicates that one entity is situated within the southwestern portion or region of another entity.
-
B.
locatedInTheSouthernHemisphere
Indicates that the subject is situated geographically south of the Earth's equator.
-
C.
locatedSouthOf
Indicates that one entity is positioned geographically to the south of another entity.
-
D.
locatedOffSouthernCoastOf
Indicates that one entity is situated in the sea or ocean area immediately to the south of another entity’s coastline.
-
E.
locatedAtSouthernFootOf
Indicates that one entity is situated at the southern base or lower slope of another entity, typically a hill, mountain, or similar landform.
- F. None of above. chosen
Provenance (4 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_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 18, 2026, 4:44 a.m.