Triple
T32597034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoyogi-Uehara |
E833244
|
entity |
| Predicate | hasAdjacentStationOnChiyodaLine |
P122294
|
FINISHED |
| Object | Yoyogi-Koen Station |
—
|
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: Yoyogi-Koen Station | Statement: [Yoyogi-Uehara, hasAdjacentStationOnChiyodaLine, Yoyogi-Koen Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationOnChiyodaLine Context triple: [Yoyogi-Uehara, hasAdjacentStationOnChiyodaLine, Yoyogi-Koen Station]
-
A.
hasAdjacentStationOnYurakuchoLine
Indicates that one station is directly next to another station along the Yurakucho Line.
-
B.
adjacentToStationOnChiyodaLine
chosen
Indicates that one entity is directly next to or neighboring a station located on the Chiyoda railway line.
-
C.
hasAdjacentStationOnFukutoshinLine
Indicates that one station is directly next to another station along the Fukutoshin railway line.
-
D.
hasAdjacentStationOnShinetsuMainLine
Indicates that one station is directly next to another station along the Shinetsu Main Line.
-
E.
hasAdjacentStationOnHankyuSenriLine
Indicates that one station is directly next to another station on the Hankyu Senri railway line.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 1:05 a.m.