Triple
T25302104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōya Subprefecture |
E634371
|
entity |
| Predicate | locatedAtExtreme |
P32351
|
FINISHED |
| Object | northernmost part of Japan |
—
|
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: northernmost part of Japan | Statement: [Sōya Subprefecture, locatedAtExtreme, northernmost part of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtExtreme Context triple: [Sōya Subprefecture, locatedAtExtreme, northernmost part of Japan]
-
A.
locatedAtTipOf
Indicates that one entity is positioned at the extreme end or tip of another entity.
-
B.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
C.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
D.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
E.
locatedAtPoleRegion
chosen
Indicates that an entity is situated within a polar region of a planetary body, such as its north or south pole area.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 21, 2026, 1:24 p.m.