Triple
T29019533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakasendō |
E737413
|
entity |
| Predicate | notablePostTown |
P14082
|
FINISHED |
| Object | Magome-juku |
E1035063
|
NE 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: Magome-juku | Statement: [Nakasendō, notablePostTown, Magome-juku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePostTown Context triple: [Nakasendō, notablePostTown, Magome-juku]
-
A.
postTown
Indicates the town or locality that serves as the postal address destination for a given address or location.
-
B.
notableReservationTown
Indicates that a town is notably associated with or recognized for a particular reservation.
-
C.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
D.
hasNotableTown
chosen
Indicates that an entity includes or is associated with a town that is considered notable or significant in some way.
-
E.
notableHumanSettlement
Indicates that a location is recognized as a significant or noteworthy human settlement, such as a city, town, or village.
- F. None of above.
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_6a01e3a2d0e08190a7d5622920dc56e6 |
completed | May 11, 2026, 2:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2505cf981081909f62473226cd3273 |
completed | June 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_6a01e3013e7881909f0cdca25a53c009 |
completed | May 11, 2026, 2:09 p.m. |
Created at: April 28, 2026, 9:48 a.m.