Triple

T37773130
Position Surface form Disambiguated ID Type / Status
Subject William Ponsonby, 2nd Earl of Bessborough E941606 entity
Predicate sibling P363 FINISHED
Object Lady Frances Ponsonby
Lady Frances Ponsonby was a member of the prominent Anglo-Irish Ponsonby aristocratic family of the 18th century.
E2250273 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: Lady Frances Ponsonby | Statement: [William Ponsonby, 2nd Earl of Bessborough, sibling, Lady Frances Ponsonby]
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: Lady Frances Ponsonby
Triple: [William Ponsonby, 2nd Earl of Bessborough, sibling, Lady Frances Ponsonby]
Generated description
Lady Frances Ponsonby was a member of the prominent Anglo-Irish Ponsonby aristocratic family of the 18th century.

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_69f76ee4431881908f87e8892a9f39f3 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbaf1f648c8190b625f91679b6f2ee completed May 6, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4117dd215c81909d412082440d7d09 completed June 28, 2026, 12:47 p.m.
NEDg Description generation batch_6a41185e9c2881908cbe2d0b8cf20961 completed June 28, 2026, 12:49 p.m.
NED2 Entity disambiguation (via description) batch_6a41228fee448190b092ddeb1c00325d completed June 28, 2026, 1:33 p.m.
Created at: May 3, 2026, 4:19 p.m.