Triple

T26183645
Position Surface form Disambiguated ID Type / Status
Subject Masaharu Morimoto E654756 entity
Predicate hasRestaurant P4442 FINISHED
Object Morimoto Waikiki (former)
Morimoto Waikiki (former) was a now-closed upscale Japanese fusion restaurant in Honolulu created by Iron Chef Masaharu Morimoto.
E1709922 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: Morimoto Waikiki (former) | Statement: [Masaharu Morimoto, hasRestaurant, Morimoto Waikiki (former)]
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: Morimoto Waikiki (former)
Triple: [Masaharu Morimoto, hasRestaurant, Morimoto Waikiki (former)]
Generated description
Morimoto Waikiki (former) was a now-closed upscale Japanese fusion restaurant in Honolulu created by Iron Chef Masaharu Morimoto.

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_69ee5b469bc081908fe486453fdad810 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60c72995481909d7e33abb0df2298 completed May 2, 2026, 2:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a112781e3d88190aef9a8e1b5f741dc completed May 23, 2026, 4:05 a.m.
NEDg Description generation batch_6a112a8d26d081909692e0fdeb070f87 completed May 23, 2026, 4:18 a.m.
NED2 Entity disambiguation (via description) batch_6a112af6fa808190821831dd3ef24648 completed May 23, 2026, 4:20 a.m.
Created at: April 26, 2026, 8:41 p.m.