Triple

T24113982
Position Surface form Disambiguated ID Type / Status
Subject Gordon Cunningham E597454 entity
Predicate hasRelative P367 FINISHED
Object Cindy Cunningham
Cindy Cunningham is a fictional character from the British soap opera "Hollyoaks," known for her long-running, tumultuous storylines within the Cunningham family.
E1691394 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: Cindy Cunningham | Statement: [Gordon Cunningham, hasRelative, Cindy Cunningham]
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: Cindy Cunningham
Triple: [Gordon Cunningham, hasRelative, Cindy Cunningham]
Generated description
Cindy Cunningham is a fictional character from the British soap opera "Hollyoaks," known for her long-running, tumultuous storylines within the Cunningham family.

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_69e288c74200819098ab875b592cb39f completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1de1cf75c8190ad5352d4b290e735 completed April 29, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10c1014e9081909f2e36f6eff1cc27 completed May 22, 2026, 8:48 p.m.
NEDg Description generation batch_6a10c20f4f748190bc19a702f0788086 completed May 22, 2026, 8:52 p.m.
NED2 Entity disambiguation (via description) batch_6a10c2b0c540819086fe2b0fef3f76d1 completed May 22, 2026, 8:55 p.m.
Created at: April 17, 2026, 11:03 p.m.