Triple
T28813602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 新富士駅 |
E727579
|
entity |
| Predicate | 最寄り在来線駅 |
P165614
|
FINISHED |
| Object | 富士駅 |
—
|
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: 富士駅 | Statement: [新富士駅, 最寄り在来線駅, 富士駅]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 最寄り在来線駅 Context triple: [新富士駅, 最寄り在来線駅, 富士駅]
-
A.
nearestShinkansenStation
Indicates that one entity is the Shinkansen (bullet train) station geographically closest to the other entity.
-
B.
隣接駅
Indicates that one station is directly adjacent to another station along a railway line.
-
C.
formerTerminalStation
Indicates that a location once served as the end point (terminus) of a transportation line or route but no longer holds that status.
-
D.
nearestRailwayLine
Indicates that one railway line is the closest in distance to a given location or feature compared to all other railway lines.
-
E.
adjacentStationOnSennichimaeLine
Indicates that one station is directly next to another station along the Sennichimae railway line.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:32 a.m.