Triple
T16265164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N700-8000 series |
E394856
|
entity |
| Predicate | serviceType |
P87
|
FINISHED |
| Object | Tsubame |
E389801
|
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: Tsubame | Statement: [N700-8000 series, serviceType, Tsubame]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tsubame Context triple: [N700-8000 series, serviceType, Tsubame]
-
A.
Tsubame
chosen
Tsubame is a Japanese Shinkansen train service that operates on the Kyushu Shinkansen line in southern Japan.
-
B.
Tsubame
Tsubame is a city in Japan renowned for its high-quality metalworking and cutlery industries.
-
C.
Tsuru
Tsuru is a small city in Yamanashi Prefecture, Japan, known for its scenic setting near Mount Fuji and its educational institutions.
-
D.
Murai
Murai is a Japanese surname borne by various notable individuals across fields such as film, music, and sports.
-
E.
Akahige
Akahige is the Japanese name for the Japanese robin, a small passerine bird native to East Asia known for its bright orange-red face and breast.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c73944819085633e6d2a69bae9 |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0017b877088190893a1f012e5d2463 |
completed | May 10, 2026, 5:29 a.m. |
Created at: April 10, 2026, 5:05 a.m.