Triple

T28210253
Position Surface form Disambiguated ID Type / Status
Subject Hatoyama family E711140 entity
Predicate hasNotableMember P304 FINISHED
Object Hatoyama Hiroko
Hatoyama Hiroko is a member of Japan’s influential Hatoyama political dynasty, known for its long-standing prominence in the country’s political and social spheres.
E1816091 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: Hatoyama Hiroko | Statement: [Hatoyama family, hasNotableMember, Hatoyama Hiroko]
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: Hatoyama Hiroko
Triple: [Hatoyama family, hasNotableMember, Hatoyama Hiroko]
Generated description
Hatoyama Hiroko is a member of Japan’s influential Hatoyama political dynasty, known for its long-standing prominence in the country’s political and social spheres.

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_69efb51cb5288190818c1f63a266af11 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f64310b67481908c2de1bc652d4d87 completed May 2, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1632e95b6481909298211bc51a1ba9 completed May 26, 2026, 11:55 p.m.
NEDg Description generation batch_6a1634e773588190b0eda7b51b029b11 completed May 27, 2026, 12:03 a.m.
NED2 Entity disambiguation (via description) batch_6a1635789f2c8190ade17d4f34d65def completed May 27, 2026, 12:06 a.m.
Created at: April 27, 2026, 10:38 p.m.