Triple
T38622174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odawara-juku |
E936899
|
entity |
| Predicate | positionInRoute |
P113827
|
FINISHED |
| Object | ninth station on the Tōkaidō |
—
|
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: ninth station on the Tōkaidō | Statement: [Odawara-juku, positionInRoute, ninth station on the Tōkaidō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRoute Context triple: [Odawara-juku, positionInRoute, ninth station on the Tōkaidō]
-
A.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
B.
pilgrimageRoutePosition
chosen
Indicates the relative location or stage of an entity along a designated pilgrimage route.
-
C.
positionInTrain
Indicates the relative location or ordering of an entity within the sequence of cars or sections that make up a train.
-
D.
relativePositionOnCourse
Indicates the positional relationship of one participant or object relative to another along a defined course or route.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.