Triple

T33386693
Position Surface form Disambiguated ID Type / Status
Subject Kuroishi, Aomori E854931 entity
Predicate hasRoadConnection P385 FINISHED
Object National Route 394
National Route 394 is a national highway in Japan that runs through Aomori Prefecture, connecting inland communities such as Kuroishi with other regional routes and destinations.
E2239499 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: National Route 394 | Statement: [Kuroishi, Aomori, hasRoadConnection, National Route 394]
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: National Route 394
Triple: [Kuroishi, Aomori, hasRoadConnection, National Route 394]
Generated description
National Route 394 is a national highway in Japan that runs through Aomori Prefecture, connecting inland communities such as Kuroishi with other regional routes and destinations.

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_69f6e3e056648190a43a9a09544e8510 completed May 3, 2026, 5:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a40cd9a6d788190b234b738c8d7c084 completed June 28, 2026, 7:30 a.m.
NEDg Description generation batch_6a40ce5899208190bd9ce55470abe0e7 completed June 28, 2026, 7:33 a.m.
NED2 Entity disambiguation (via description) batch_6a40cf3590c48190988529eb57a92a9e completed June 28, 2026, 7:37 a.m.
Created at: May 1, 2026, 1:35 a.m.