Triple

T27437817
Position Surface form Disambiguated ID Type / Status
Subject Margaret of Burgundy E690837 entity
Predicate title P38 FINISHED
Object Countess of Flanders
The Countess of Flanders was a powerful medieval noblewoman who ruled the wealthy and strategically important County of Flanders in northwestern Europe.
E378847 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: Countess of Flanders | Statement: [Margaret of Burgundy, title, Countess of Flanders]
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: Countess of Flanders
Triple: [Margaret of Burgundy, title, Countess of Flanders]
Generated description
The Countess of Flanders was a powerful medieval noblewoman who ruled the wealthy and strategically important County of Flanders in northwestern Europe.

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_69ef5200fa0481908e28508d6e2c149e completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62d8b2050819096bdc6539e8cb099 completed May 2, 2026, 4:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a273200d25c8190aea53241e65ff104 completed June 8, 2026, 9:20 p.m.
NEDg Description generation batch_6a27344392f8819096430da00dda75a1 completed June 8, 2026, 9:29 p.m.
NED2 Entity disambiguation (via description) batch_6a2734c2d13c8190b7401d9b7d6d8fed completed June 8, 2026, 9:31 p.m.
Created at: April 27, 2026, 12:44 p.m.