Triple
T38665109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 京浜急行電鉄株式会社 |
E940432
|
entity |
| Predicate | 本社最寄り駅 |
P178482
|
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.
最寄り在来線駅
Indicates the relationship where a given location is associated with its nearest conventional (non-high-speed) railway station.
-
B.
代表的駅
Indicates that one entity serves as the representative or main station for another entity (such as a city, area, or organization).
-
C.
最寄施設
chosen
Indicates a relationship where one facility is the nearest or most conveniently located facility relative to a given reference point or entity.
-
D.
主な発着駅
Indicates that one entity serves as the primary departure and arrival station associated with another entity (such as a route, service, or line).
-
E.
最寄り自治体
Indicates the relationship where a given place or entity is associated with the geographically nearest local government/municipality responsible for it.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.