Triple

T36968360
Position Surface form Disambiguated ID Type / Status
Subject Doug Stanhope E914489 entity
Predicate spouse P13 FINISHED
Object Bingo (Amy Tegtmeyer)
Bingo (Amy Tegtmeyer) is an American performer and writer best known as comedian Doug Stanhope’s longtime partner and frequent collaborator in his projects.
E2206875 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: Bingo (Amy Tegtmeyer) | Statement: [Doug Stanhope, spouse, Bingo (Amy Tegtmeyer)]
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: Bingo (Amy Tegtmeyer)
Triple: [Doug Stanhope, spouse, Bingo (Amy Tegtmeyer)]
Generated description
Bingo (Amy Tegtmeyer) is an American performer and writer best known as comedian Doug Stanhope’s longtime partner and frequent collaborator in his projects.

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_69f76e8c498c8190b2842db80aea8b3b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9ff3e0728819091a386e671e1f046 completed May 5, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3e2c43e86c8190aaa8369455a02a52 completed June 26, 2026, 7:37 a.m.
NEDg Description generation batch_6a3e2ce08a40819081db007321d0b279 completed June 26, 2026, 7:40 a.m.
NED2 Entity disambiguation (via description) batch_6a3e458016e881909cef925bc1bad341 completed June 26, 2026, 9:25 a.m.
Created at: May 3, 2026, 4:14 p.m.