Triple

T33386680
Position Surface form Disambiguated ID Type / Status
Subject Kuroishi, Aomori E854931 entity
Predicate hasTraditionalDistrict P49478 FINISHED
Object Komise Street
Komise Street is a historic, traditional shopping and merchant district in Kuroishi, Aomori, known for its preserved Edo-period covered walkways and wooden townscape.
E2062965 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: Komise Street | Statement: [Kuroishi, Aomori, hasTraditionalDistrict, Komise Street]
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: Komise Street
Triple: [Kuroishi, Aomori, hasTraditionalDistrict, Komise Street]
Generated description
Komise Street is a historic, traditional shopping and merchant district in Kuroishi, Aomori, known for its preserved Edo-period covered walkways and wooden townscape.

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_69f3496d54048190a1cb91fdd7caa6ea completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3df72ec819084033f6cf89e947e completed May 3, 2026, 5:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a363c77d1d88190a052e4be57921c78 completed June 20, 2026, 7:08 a.m.
NEDg Description generation batch_6a36428331d48190a9caab0618254d48 completed June 20, 2026, 7:34 a.m.
NED2 Entity disambiguation (via description) batch_6a3643d62ce88190bce91a044daa6798 completed June 20, 2026, 7:40 a.m.
Created at: May 1, 2026, 1:35 a.m.