Triple
T37831496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōtsu-juku |
E943214
|
entity |
| Predicate | positionOnNakasendō |
P201419
|
FINISHED |
| Object | 69th station of the 69 Stations of the Nakasendō |
—
|
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: 69th station of the 69 Stations of the Nakasendō | Statement: [Ōtsu-juku, positionOnNakasendō, 69th station of the 69 Stations of the Nakasendō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnNakasendō Context triple: [Ōtsu-juku, positionOnNakasendō, 69th station of the 69 Stations of the Nakasendō]
-
A.
positionInShikokuPilgrimage
Indicates the specific sequential position an entity holds along the route of the Shikoku pilgrimage.
-
B.
sequenceOnTōkaidō
Indicates that one entity occurs at a specific position or order along the Tōkaidō route or sequence.
-
C.
positionOnHonshu
Indicates that one entity is geographically located on the island of Honshu in Japan.
-
D.
neighboringPostTownOnTōkaidō
Indicates that two post towns are directly adjacent to each other along the historical Tōkaidō route.
-
E.
positionInJapanese
Indicates that one entity occupies a specific position or rank within a Japanese ordering, sequence, or structure.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fff327d7788190a41ea5cbae060177 |
completed | May 10, 2026, 2:53 a.m. |
Created at: May 3, 2026, 4:19 p.m.