Triple

T25634837
Position Surface form Disambiguated ID Type / Status
Subject House of Hénin-Liétard E642670 entity
Predicate notableMember P10 FINISHED
Object Charles de Hénin-Liétard
Charles de Hénin-Liétard was a prominent nobleman from the influential Belgian-French aristocratic House of Hénin-Liétard.
E2290817 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: Charles de Hénin-Liétard | Statement: [House of Hénin-Liétard, notableMember, Charles de Hénin-Liétard]
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: Charles de Hénin-Liétard
Triple: [House of Hénin-Liétard, notableMember, Charles de Hénin-Liétard]
Generated description
Charles de Hénin-Liétard was a prominent nobleman from the influential Belgian-French aristocratic House of Hénin-Liétard.

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_69e77e7bd4548190a0c691b8a2f27ff1 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5fa60db0c8190b5c615e6dc35264a completed May 2, 2026, 1:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5c039993908190bb556c9926635eaf completed July 18, 2026, 10:52 p.m.
NEDg Description generation batch_6a5c044e0d288190bdc118b0b3860a00 completed July 18, 2026, 10:55 p.m.
NED2 Entity disambiguation (via description) batch_6a5c04af78a48190aa9590b7807704ba completed July 18, 2026, 10:56 p.m.
Created at: April 21, 2026, 5:21 p.m.