Triple
T11568634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uesugi Shrine |
E274321
|
entity |
| Predicate | touristAttraction |
P530
|
FINISHED |
| Object | Yonezawa |
E1127347
|
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: Yonezawa | Statement: [Uesugi Shrine, touristAttraction, Yonezawa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yonezawa Context triple: [Uesugi Shrine, touristAttraction, Yonezawa]
-
A.
Yonezawa
chosen
Yonezawa is a city in southern Yamagata Prefecture, Japan, known for its historic castle town, high-quality Yonezawa beef, and snowy climate.
-
B.
Noshiro
Noshiro is a coastal city in northern Japan known for its port on the Sea of Japan and its forestry and basketball traditions.
-
C.
Higashikawa
Higashikawa is a town in Hokkaido, Japan, known as a gateway to the Daisetsuzan mountain range and for its scenic natural landscapes.
-
D.
Inazawa
Inazawa is a city in central Japan known for its agricultural production and historic shrines, located within Aichi Prefecture.
-
E.
Kanoya
Kanoya is a city in Kagoshima Prefecture on Japan’s Kyushu island, known as a regional center on the Ōsumi Peninsula with agricultural production and a former naval air base.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd543a48190b834abd8e8ae7b65 |
completed | April 10, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f1f80648190a4a0e8260ac95194 |
completed | May 9, 2026, 4:21 p.m. |
Created at: April 8, 2026, 9:37 p.m.