Triple
T34321026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouchi-juku |
E880734
|
entity |
| Predicate | localSpecialtyProduct |
P17971
|
FINISHED |
| Object | traditional crafts and souvenirs |
—
|
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: traditional crafts and souvenirs | Statement: [Ouchi-juku, localSpecialtyProduct, traditional crafts and souvenirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localSpecialtyProduct Context triple: [Ouchi-juku, localSpecialtyProduct, traditional crafts and souvenirs]
-
A.
shopSpecialty
Indicates that a shop primarily focuses on or is specially known for offering a particular type of product or service.
-
B.
traditionalAgriculturalProduct
Indicates that something is recognized as an agricultural product produced using long-established, customary methods and practices.
-
C.
hasSpecialtyFood
chosen
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
D.
servesProduct
Indicates that one entity provides or offers a particular product to others, typically in a commercial or service context.
-
E.
houseSpecialty
Indicates that something is the featured or signature item offered by a particular place or provider.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:57 a.m.