Triple
T35842271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsumago-juku |
E1036116
|
entity |
| Predicate | hasMainStreetType |
P461
|
FINISHED |
| Object | stone-pavedStreet |
—
|
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: stone-pavedStreet | Statement: [Tsumago-juku, hasMainStreetType, stone-pavedStreet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainStreetType Context triple: [Tsumago-juku, hasMainStreetType, stone-pavedStreet]
-
A.
hasMainStreet
chosen
Indicates that a place or locality possesses a primary street commonly recognized as its main thoroughfare.
-
B.
hasMainStreetLayout
Indicates that an area or development is organized around a central “main street” corridor that structures its layout and circulation.
-
C.
hasMainResidentialStreet
Indicates that an entity is associated with or served by a specific primary street used predominantly for residential purposes.
-
D.
isMainRoad
Indicates that a road serves as a primary or major thoroughfare within a transportation network.
-
E.
isMajorCommercialStreetOf
Indicates that a street serves as a primary, heavily used route for commercial activity within a specified area or locality.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0302d9d2d88190b20429530775b035 |
completed | May 12, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_6a0302289128819085428f3d544c2fb9 |
completed | May 12, 2026, 10:34 a.m. |
Created at: May 3, 2026, 4:06 p.m.