Triple

T29267002
Position Surface form Disambiguated ID Type / Status
Subject Margaret III, Countess of Flanders E742002 entity
Predicate nobleTitle P914 FINISHED
Object Countess of Nevers
The Countess of Nevers was a medieval French noble title associated with the rulership of the County of Nevers in central France.
E1902570 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 Nevers | Statement: [Margaret III, Countess of Flanders, nobleTitle, Countess of Nevers]
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 Nevers
Triple: [Margaret III, Countess of Flanders, nobleTitle, Countess of Nevers]
Generated description
The Countess of Nevers was a medieval French noble title associated with the rulership of the County of Nevers in central France.

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_69f0912065c08190bddd23e20e8ef18e completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f664e055c08190a60b01ef9238de79 completed May 2, 2026, 8:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2757d9060c819088686744787d7e08 completed June 9, 2026, 12:01 a.m.
NEDg Description generation batch_6a275a4311f08190b067b8c94e48d019 completed June 9, 2026, 12:11 a.m.
NED2 Entity disambiguation (via description) batch_6a275aeeed3c8190ba20d38ec0af1c74 completed June 9, 2026, 12:14 a.m.
Created at: April 28, 2026, 12:45 p.m.