Triple
T2868541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokaido Shinkansen |
E63499
|
entity |
| Predicate | routeFollows |
P2127
|
FINISHED |
| Object | historical Tokaido corridor |
—
|
LITERAL 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: historical Tokaido corridor | Statement: [Tokaido Shinkansen, routeFollows, historical Tokaido corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeFollows Context triple: [Tokaido Shinkansen, routeFollows, historical Tokaido corridor]
-
A.
followsRouteOf
chosen
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
C.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
D.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
E.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
- F. None of above.
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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfdfef1881909dc52a1b34cd24e3 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.