Triple
T29019522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakasendō |
E737413
|
entity |
| Predicate | hasNumberOfPostTowns |
P191891
|
FINISHED |
| Object | 69 |
—
|
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: 69 | Statement: [Nakasendō, hasNumberOfPostTowns, 69]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfPostTowns Context triple: [Nakasendō, hasNumberOfPostTowns, 69]
-
A.
hasNumberOfMunicipalities
Indicates the relationship that specifies how many municipalities are associated with or contained within a given administrative or geographic entity.
-
B.
hasNumberOfRuralSettlements
Indicates the quantity of rural settlements associated with or contained within a given entity.
-
C.
hasPostcodeAreasAlong
Indicates that a geographic feature or route is associated with, or passes through, specific postcode areas along its extent.
-
D.
hasPostalTownStatus
Indicates that an entity holds the official designation or status of being a postal town within a postal addressing system.
-
E.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
- 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_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: April 28, 2026, 9:48 a.m.