Triple
T21957434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissaka-juku |
E542228
|
entity |
| Predicate | sequenceOnTōkaidō |
P146696
|
FINISHED |
| Object | 25th station |
—
|
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: 25th station | Statement: [Nissaka-juku, sequenceOnTōkaidō, 25th station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceOnTōkaidō Context triple: [Nissaka-juku, sequenceOnTōkaidō, 25th station]
-
A.
positionInShikokuPilgrimage
Indicates the specific sequential position an entity holds along the route of the Shikoku pilgrimage.
-
B.
rankWithinKamakuraGozan
Indicates the position or level an entity holds within the hierarchical ranking system of the Kamakura Gozan (the Five Great Zen Temples of Kamakura).
-
C.
SeikanTunnelConnects
Indicates that the Seikan Tunnel serves as a physical connection between two geographic locations or regions.
-
D.
SeikanTunnelType
Indicates that one entity is classified as a specific type or category of Seikan Tunnel.
-
E.
successorInServiceOnTokaido
Indicates that one entity took over or followed another in providing service on the Tokaido route or line.
- F. None of above. chosen
Provenance (4 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1244108948190a08e6966e55c4acd |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb9b75308190addc3dba7b5d5ddd |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:59 p.m.