Triple

T35049771
Position Surface form Disambiguated ID Type / Status
Subject Hōjō Ujiyasu E1011295 entity
Predicate child P120 FINISHED
Object Hōjō Ujinori
Hōjō Ujinori was a late Sengoku-period samurai and daimyō of the Later Hōjō clan, known for his role in the clan’s final years and his service under Tokugawa Ieyasu after their fall.
E2284818 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: Hōjō Ujinori | Statement: [Hōjō Ujiyasu, child, Hōjō Ujinori]
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: Hōjō Ujinori
Triple: [Hōjō Ujiyasu, child, Hōjō Ujinori]
Generated description
Hōjō Ujinori was a late Sengoku-period samurai and daimyō of the Later Hōjō clan, known for his role in the clan’s final years and his service under Tokugawa Ieyasu after their fall.

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_69f76dcfdda48190b1ebae5da8b54f12 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f785ca8fa4819088713fd7a58fa229 completed May 3, 2026, 5:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a44a358447c81908baf52ba9c329f15 completed July 1, 2026, 5:19 a.m.
NEDg Description generation batch_6a44a4259a588190ac5e415d6796c8f0 completed July 1, 2026, 5:22 a.m.
NED2 Entity disambiguation (via description) batch_6a44a59a4e7081909521e8a5af0f7e13 completed July 1, 2026, 5:28 a.m.
Created at: May 3, 2026, 4:01 p.m.