Triple
T29044971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōya Main Line |
E738107
|
entity |
| Predicate | northernmostLineIn |
P118286
|
FINISHED |
| Object | Japan Railways Group network |
—
|
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 Railways Group network | Statement: [Sōya Main Line, northernmostLineIn, Japan Railways Group network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernmostLineIn Context triple: [Sōya Main Line, northernmostLineIn, Japan Railways Group network]
-
A.
northernmostPoint
Indicates the location that lies furthest to the north within the spatial extent of a given entity.
-
B.
isNorthernmost
Indicates that one entity is located farther north than all other comparable entities in a given set or region.
-
C.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
-
D.
isNorthernmostCityOf
Indicates that a city is the one located furthest to the north within a specified region, area, or set of cities.
-
E.
northernmostStatus
chosen
Indicates that an entity holds the distinction of being the furthest north (e.g., most northerly location) within a specified set, category, or context.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:04 a.m.