Triple

T14614727
Position Surface form Disambiguated ID Type / Status
Subject Ohno E343054 entity
Predicate hasNotableBearer P458 FINISHED
Object Yasuo Ohno
Yasuo Ohno is a Japanese individual notable enough to be recognized as a distinct namesake of the surname Ohno.
E1801748 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: Yasuo Ohno | Statement: [Ohno, hasNotableBearer, Yasuo Ohno]
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: Yasuo Ohno
Triple: [Ohno, hasNotableBearer, Yasuo Ohno]
Generated description
Yasuo Ohno is a Japanese individual notable enough to be recognized as a distinct namesake of the surname Ohno.

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_69d822dec68081908c2553145c4051dc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb45264988190a1df13e8b54a85bd completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15c8ca42288190b6336ab3e05b253c completed May 26, 2026, 4:22 p.m.
NEDg Description generation batch_6a15cac6172c8190b677d538dee18fb0 completed May 26, 2026, 4:31 p.m.
NED2 Entity disambiguation (via description) batch_6a15cb48691081909c5dde3e9a0db8f4 completed May 26, 2026, 4:33 p.m.
Created at: April 10, 2026, 1:25 a.m.