Triple

T25753933
Position Surface form Disambiguated ID Type / Status
Subject Duke of Westphalia E648539 entity
Predicate officeHolder P537 FINISHED
Object Konrad von Hochstaden
Konrad von Hochstaden was a 13th-century German nobleman and ecclesiastical prince who played a significant role in the politics of the Holy Roman Empire.
E1738304 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: Konrad von Hochstaden | Statement: [Duke of Westphalia, officeHolder, Konrad von Hochstaden]
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: Konrad von Hochstaden
Triple: [Duke of Westphalia, officeHolder, Konrad von Hochstaden]
Generated description
Konrad von Hochstaden was a 13th-century German nobleman and ecclesiastical prince who played a significant role in the politics of the Holy Roman Empire.

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_69e7ab314d788190b3abe19e114080e1 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f5fd80a93081909fa651bc57d26884 completed May 2, 2026, 1:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe449f6881909fd44c32aa09131d completed May 23, 2026, 7:21 p.m.
NEDg Description generation batch_6a11fef3277c81909157e7d7caa3245b completed May 23, 2026, 7:24 p.m.
NED2 Entity disambiguation (via description) batch_6a11fffd6b1081909ed36e05ffdaed73 completed May 23, 2026, 7:29 p.m.
Created at: April 22, 2026, 4:38 a.m.