Triple

T21317977
Position Surface form Disambiguated ID Type / Status
Subject Tomioka E525527 entity
Predicate hasNotableBearer P458 FINISHED
Object Tomioka Minoru
Tomioka Minoru is a Japanese individual notable for bearing the surname Tomioka, though specific widely recognized public achievements or roles are not well documented.
E2152350 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: Tomioka Minoru | Statement: [Tomioka, hasNotableBearer, Tomioka Minoru]
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: Tomioka Minoru
Triple: [Tomioka, hasNotableBearer, Tomioka Minoru]
Generated description
Tomioka Minoru is a Japanese individual notable for bearing the surname Tomioka, though specific widely recognized public achievements or roles are not well documented.

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_69e0b51ad810819098c12392c8e55f6c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75dd1ce9c81908c373362254427bf completed April 21, 2026, 11:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a387cec24148190ad5f77e0f1221f4f completed June 22, 2026, 12:08 a.m.
NEDg Description generation batch_6a387d8bebac8190945e3bd73b0e9222 completed June 22, 2026, 12:10 a.m.
NED2 Entity disambiguation (via description) batch_6a387dfd11588190b56499799b37f578 completed June 22, 2026, 12:12 a.m.
Created at: April 16, 2026, 4:36 p.m.