Triple
T20489620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keikyū Main Line |
E502702
|
entity |
| Predicate | hasJapaneseName |
P9882
|
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: [Keikyū Main Line, hasJapaneseName, 京急本線]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 京急本線 Context triple: [Keikyū Main Line, hasJapaneseName, 京急本線]
-
A.
京急本線
chosen
京急本線は東京都心と神奈川県の横浜・三浦半島方面を結ぶ京浜急行電鉄の主要な幹線鉄道路線です。
-
B.
東急池上線
東急池上線 is a Tokyu Corporation commuter railway line in Tokyo that connects Gotanda and Kamata, serving several residential and commercial districts along its route.
-
C.
東急大井町線
東急大井町線 is a major Tokyu Corporation commuter railway line in Tokyo that connects Ōimachi with suburban areas such as Futako-Tamagawa and serves key residential and commercial districts.
-
D.
京浜東北線
京浜東北線は、東京都心と神奈川・埼玉方面を南北に結び、東海道線・東北本線と並行して運行されるJR東日本の主要通勤路線です。
-
E.
横須賀線
横須賀線 is a major JR East railway line in the Greater Tokyo and Kanagawa area that connects central Tokyo with Yokosuka and the Miura Peninsula.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b5d93ec81908259696359090b35 |
completed | April 20, 2026, 9:32 p.m. |
Created at: April 16, 2026, 11:34 a.m.