Triple
T19604301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 柏崎市 |
E470563
|
entity |
| Predicate | hasHighway |
P385
|
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: [柏崎市, hasHighway, 北陸自動車道]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 北陸自動車道 Context triple: [柏崎市, hasHighway, 北陸自動車道]
-
A.
東海北陸自動車道
東海北陸自動車道 is a major Japanese expressway that links the Tōkai and Hokuriku regions, running primarily through central Honshu and serving as an important north–south transportation corridor.
-
B.
Hokuriku Expressway
chosen
The Hokuriku Expressway is a major Japanese expressway running along the Sea of Japan coast, linking the Hokuriku region with central and western Honshu.
-
C.
中国自動車道
中国自動車道は、本州西部の中国地方を東西に横断し、大阪方面と山口県・九州方面を結ぶ日本の主要高速自動車国道である。
-
D.
Aomori Expressway
The Aomori Expressway is a regional expressway in Aomori Prefecture, Japan, that connects local routes to the national expressway network.
-
E.
Hachinohe Expressway
The Hachinohe Expressway is a major national expressway in northeastern Japan that connects the city of Hachinohe in Aomori Prefecture with the wider Tōhoku expressway network.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64081af6c8190868b73b07c874cd5 |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.