Triple

T36014570
Position Surface form Disambiguated ID Type / Status
Subject Peter Alliss E1041801 entity
Predicate relative P37 FINISHED
Object Percy Alliss
Percy Alliss was a prominent English professional golfer of the early 20th century, known both for his tournament success and as the father of famed golf commentator Peter Alliss.
E2168796 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: Percy Alliss | Statement: [Peter Alliss, relative, Percy Alliss]
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: Percy Alliss
Triple: [Peter Alliss, relative, Percy Alliss]
Generated description
Percy Alliss was a prominent English professional golfer of the early 20th century, known both for his tournament success and as the father of famed golf commentator Peter Alliss.

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_69f76e2b981881908e4e160607fa82eb completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7acb62b748190891abc766a339b23 completed May 3, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38d52bf05881908ca033d0cd0db9c2 completed June 22, 2026, 6:24 a.m.
NEDg Description generation batch_6a38d5fbbf84819083a18d64edddbbe6 completed June 22, 2026, 6:28 a.m.
NED2 Entity disambiguation (via description) batch_6a38d69d54f48190b43baa60bfa8fe85 completed June 22, 2026, 6:30 a.m.
Created at: May 3, 2026, 4:07 p.m.