Triple
T15125606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keikyū Airport Line |
E361280
|
entity |
| Predicate | hasJapaneseName |
P9882
|
FINISHED |
| Object | 京急空港線 |
E361280
|
NE FINISHED |
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ū Airport Line, hasJapaneseName, 京急空港線]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 京急空港線 Context triple: [Keikyū Airport Line, hasJapaneseName, 京急空港線]
-
A.
東急大井町線
東急大井町線 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.
-
B.
Keikyū Airport Line
chosen
The Keikyū Airport Line is a railway line in the Tokyo area that provides direct train access between central Tokyo and Haneda Airport.
-
C.
Narita Airport Line (Keisei)
The Narita Airport Line (Keisei) is a Japanese railway line operated by Keisei Electric Railway that provides rapid rail access between central Tokyo and Narita International Airport.
-
D.
高崎線
高崎線は、東京都と群馬県高崎市方面を結ぶ日本の主要な幹線鉄道路線の一つです。
-
E.
Keio Sagamihara Line
The Keio Sagamihara Line is a commuter railway line in the Tokyo metropolitan area operated by Keio Corporation, connecting suburban communities with central Tokyo.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a1b9288190954f2d92549805e5 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feb7f67f6c81909723c13255306668 |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 3:06 a.m.