Triple

T27726109
Position Surface form Disambiguated ID Type / Status
Subject Frederick I, Count of Mark E699100 entity
Predicate mother P120 FINISHED
Object Ermengarde of Berg
Ermengarde of Berg was a medieval noblewoman from the House of Berg who became Countess of the Mark and the mother of Frederick I, Count of Mark.
E1922950 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: Ermengarde of Berg | Statement: [Frederick I, Count of Mark, mother, Ermengarde of Berg]
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: Ermengarde of Berg
Triple: [Frederick I, Count of Mark, mother, Ermengarde of Berg]
Generated description
Ermengarde of Berg was a medieval noblewoman from the House of Berg who became Countess of the Mark and the mother of Frederick I, Count of Mark.

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_69ef591012dc8190a6f1ec994f9f7ff7 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f6364042dc8190a2dc2133ec220baa completed May 2, 2026, 5:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2863ade8e0819088662c89d60dfc7c completed June 9, 2026, 7:04 p.m.
NEDg Description generation batch_6a286543299c8190b9ab7af03d898603 completed June 9, 2026, 7:10 p.m.
NED2 Entity disambiguation (via description) batch_6a2865bb31c48190bd82b4e19b0fedcc completed June 9, 2026, 7:12 p.m.
Created at: April 27, 2026, 3:09 p.m.