Triple
T14016687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 六甲アイランド |
E337221
|
entity |
| Predicate | 鉄道路線 |
P848
|
FINISHED |
| Object | 六甲ライナー |
E1224960
|
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: [六甲アイランド, 鉄道路線, 六甲ライナー]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 六甲ライナー Context triple: [六甲アイランド, 鉄道路線, 六甲ライナー]
-
A.
六甲ライナー
chosen
六甲ライナーは、神戸市の人工島である六甲アイランドと本土側を結ぶ新交通システム（自動案内軌条式旅客輸送システム）です。
-
B.
Yurikamome Line
The Yurikamome Line is an automated, elevated transit line in Tokyo that connects central Tokyo with the Odaiba waterfront area, offering scenic views including a crossing of the Rainbow Bridge.
-
C.
Minatomirai Line
The Minatomirai Line is a private railway line in Yokohama, Japan, connecting central Yokohama with the Minato Mirai 21 waterfront district and offering through services with multiple Tokyo subway and suburban lines.
-
D.
Oimachi Line
The Oimachi Line is a commuter railway line in Tokyo, Japan, forming part of the Tokyu network and connecting central Tokyo with its southwestern suburbs.
-
E.
Imazatosuji Line
The Imazatosuji Line is a rapid transit line in Osaka, Japan, operated by Osaka Metro and serving as one of the city’s main north–south subway corridors.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f396b648190927e5718c3bb6511 |
completed | April 14, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00a4fffa7c81909bcc833b44ddf66f |
completed | May 10, 2026, 3:32 p.m. |
Created at: April 9, 2026, 10:19 p.m.