Triple

T19286206
Position Surface form Disambiguated ID Type / Status
Subject Semboku E482317 entity
Predicate hasHistoricDistrict P295 FINISHED
Object Kakunodate
Kakunodate is a well-preserved former samurai town in Akita Prefecture, Japan, renowned for its historic streets lined with traditional samurai residences and cherry trees.
E1692318 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: Kakunodate | Statement: [Semboku, hasHistoricDistrict, Kakunodate]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kakunodate
Triple: [Semboku, hasHistoricDistrict, Kakunodate]
Generated description
Kakunodate is a well-preserved former samurai town in Akita Prefecture, Japan, renowned for its historic streets lined with traditional samurai residences and cherry trees.

Provenance (5 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_69d8e8cf61b0819096fe3e4107827c4e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fc024a7081909a25d7cc4e048f79 completed April 20, 2026, 10:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10cb9f271881909c6b0cab56f96423 completed May 22, 2026, 9:33 p.m.
NEDg Description generation batch_6a10cc4b6a148190bd5e4f15b4865bd6 completed May 22, 2026, 9:36 p.m.
NED2 Entity disambiguation (via description) batch_6a10ccc0f98081908f4819dd1f61c492 completed May 22, 2026, 9:38 p.m.
Created at: April 10, 2026, 1:30 p.m.