Triple
T29044972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōya Main Line |
E738107
|
entity |
| Predicate | northernmostTerminusIn |
P63399
|
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: [Sōya Main Line, northernmostTerminusIn, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernmostTerminusIn Context triple: [Sōya Main Line, northernmostTerminusIn, Japan]
-
A.
northernTerminusConnects
Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
-
B.
northernmostPoint
Indicates the location that lies furthest to the north within the spatial extent of a given entity.
-
C.
northernTerminusMunicipality
chosen
Indicates that a municipality serves as the northern endpoint or terminus of a route, line, or similar linear feature.
-
D.
northernTerminusVariant
Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
-
E.
northernTerminusCity
Indicates that one city serves as the northern endpoint or final stop of a route, line, or corridor relative to another location.
- 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_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 10:04 a.m.