Triple

T36052946
Position Surface form Disambiguated ID Type / Status
Subject Tokugawa Mitsukuni E1042862 entity
Predicate successor P78 FINISHED
Object Tokugawa Tsunaeda
Tokugawa Tsunaeda was a daimyō of the Mito Domain in Japan’s Edo period, known primarily as the heir and successor within the prominent Mito branch of the Tokugawa clan.
E2279964 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: Tokugawa Tsunaeda | Statement: [Tokugawa Mitsukuni, successor, Tokugawa Tsunaeda]
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: Tokugawa Tsunaeda
Triple: [Tokugawa Mitsukuni, successor, Tokugawa Tsunaeda]
Generated description
Tokugawa Tsunaeda was a daimyō of the Mito Domain in Japan’s Edo period, known primarily as the heir and successor within the prominent Mito branch of the Tokugawa clan.

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_69f76e2e41f8819091f9fb0536920fec completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7b1e5cee88190a767176ef76e63c2 completed May 3, 2026, 8:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41fd3bd4fc819091e8c8077a6ef460 completed June 29, 2026, 5:06 a.m.
NEDg Description generation batch_6a41fe3f00d08190ae597e4266b901ee completed June 29, 2026, 5:10 a.m.
NED2 Entity disambiguation (via description) batch_6a41fef909448190bb059bf9b7f7e5c6 completed June 29, 2026, 5:13 a.m.
Created at: May 3, 2026, 4:07 p.m.