Triple

T26969355
Position Surface form Disambiguated ID Type / Status
Subject Húrin Thalion E679264 entity
Predicate curseTarget P7531 FINISHED
Object House of Húrin
The House of Húrin is a noble family of Men in J.R.R. Tolkien’s legendarium, renowned for its valor in the First Age and tragically marked by Morgoth’s devastating curse.
E1751339 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: House of Húrin | Statement: [Húrin Thalion, curseTarget, House of Húrin]
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: House of Húrin
Triple: [Húrin Thalion, curseTarget, House of Húrin]
Generated description
The House of Húrin is a noble family of Men in J.R.R. Tolkien’s legendarium, renowned for its valor in the First Age and tragically marked by Morgoth’s devastating curse.

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_69eeeb4f3a448190b1e94b2d4776c16e completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f621233f2c81908c237f20c50c2ba3 completed May 2, 2026, 4:06 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12e42f749c8190828b02fa6eba7229 completed May 24, 2026, 11:42 a.m.
NEDg Description generation batch_6a12e4da65dc8190801cafed5fb95685 completed May 24, 2026, 11:45 a.m.
NED2 Entity disambiguation (via description) batch_6a12e5acc5c8819081be9900ea407d65 completed May 24, 2026, 11:49 a.m.
Created at: April 27, 2026, 6:38 a.m.