Triple
T29019517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakasendō |
E737413
|
entity |
| Predicate | distinctionFromTōkaidō |
P167941
|
FINISHED |
| Object | ran inland rather than along the coast |
—
|
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: ran inland rather than along the coast | Statement: [Nakasendō, distinctionFromTōkaidō, ran inland rather than along the coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinctionFromTōkaidō Context triple: [Nakasendō, distinctionFromTōkaidō, ran inland rather than along the coast]
-
A.
sequenceOnTōkaidō
Indicates that one entity occurs at a specific position or order along the Tōkaidō route or sequence.
-
B.
locatedInDirectionFromTokyo
Indicates that one place is situated in a specified compass direction relative to Tokyo.
-
C.
regionOfJapan
Indicates that one entity is a geographic region that is part of, or located within, Japan.
-
D.
SeikanTunnelConnects
Indicates that the Seikan Tunnel serves as a physical connection between two geographic locations or regions.
-
E.
terminusOnHonshu
Indicates that the endpoint or terminus of something (such as a route, line, or connection) is located on the island of Honshu.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 9:48 a.m.