Triple
T14724601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series E7 Shinkansen |
E345904
|
entity |
| Predicate | usedOnService |
P2367
|
FINISHED |
| Object | Asama |
E934412
|
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: Asama | Statement: [Series E7 Shinkansen, usedOnService, Asama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asama Context triple: [Series E7 Shinkansen, usedOnService, Asama]
-
A.
Asama
chosen
Asama is a high-speed Shinkansen train service in Japan that operates primarily on the Hokuriku Shinkansen line between Tokyo and Nagano.
-
B.
Asama
Asama was a Japanese armored cruiser of the Imperial Japanese Navy that served prominently in the Russo-Japanese War.
-
C.
Mount Asama
Mount Asama is an active and prominent volcano in central Honshu, Japan, known for its frequent eruptions and status as one of the country’s most closely monitored peaks.
-
D.
Mount Ishizuchi
Mount Ishizuchi is a prominent and sacred peak in western Japan, renowned as one of the country's Seven Holy Mountains and a popular destination for hiking and pilgrimage.
-
E.
Eboshidake
Eboshidake is a mountain in Japan, known as one of the peaks in the volcanic landscape of the Kirishima mountain range on Kyushu.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec25e9a14819081fa06fc601f295d |
completed | April 14, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe64ee4284819093db172023e9fe87 |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:29 a.m.