Triple

T25603667
Position Surface form Disambiguated ID Type / Status
Subject Henry I, Landgrave of Hesse E641850 entity
Predicate child P120 FINISHED
Object Adelheid of Hesse
Adelheid of Hesse was a medieval German noblewoman from the ruling house of Hesse, known primarily as a daughter of Henry I, the first Landgrave of Hesse.
E1962505 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: Adelheid of Hesse | Statement: [Henry I, Landgrave of Hesse, child, Adelheid of Hesse]
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: Adelheid of Hesse
Triple: [Henry I, Landgrave of Hesse, child, Adelheid of Hesse]
Generated description
Adelheid of Hesse was a medieval German noblewoman from the ruling house of Hesse, known primarily as a daughter of Henry I, the first Landgrave of Hesse.

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_69e75dc6ccf081908d49578fd36a76d5 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f9a89830819083b11f0b818e538d completed May 2, 2026, 1:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2b07470af8819090cca4cf72202805 completed June 11, 2026, 7:06 p.m.
NEDg Description generation batch_6a2b085b9e308190bc6b372a8555f07f completed June 11, 2026, 7:11 p.m.
NED2 Entity disambiguation (via description) batch_6a2b08ed93d081908aeb1dd316e9ab21 completed June 11, 2026, 7:13 p.m.
Created at: April 21, 2026, 4:36 p.m.