Triple

T24972705
Position Surface form Disambiguated ID Type / Status
Subject Sophie, Countess of Vence E624934 entity
Predicate nameInFrench P6538 FINISHED
Object Sophie, comtesse de Vence
Sophie, comtesse de Vence is a French noblewoman historically known by her aristocratic title as the Countess of Vence.
E1736792 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: Sophie, comtesse de Vence | Statement: [Sophie, Countess of Vence, nameInFrench, Sophie, comtesse de Vence]
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: Sophie, comtesse de Vence
Triple: [Sophie, Countess of Vence, nameInFrench, Sophie, comtesse de Vence]
Generated description
Sophie, comtesse de Vence is a French noblewoman historically known by her aristocratic title as the Countess of Vence.

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_69e2ff24512481908e9a72315b8d0354 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f444de84408190b69cc03c458d6195 completed May 1, 2026, 6:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe3e8f448190b1594398ba2918fc completed May 23, 2026, 7:21 p.m.
NEDg Description generation batch_6a11ff162d588190a1f98429d7fe5154 completed May 23, 2026, 7:25 p.m.
NED2 Entity disambiguation (via description) batch_6a11ff99fdbc81909fd5646fb32987a2 completed May 23, 2026, 7:27 p.m.
Created at: April 18, 2026, 6:01 a.m.