Triple

T29890965
Position Surface form Disambiguated ID Type / Status
Subject Huntley E759147 entity
Predicate hasNotableBearer P458 FINISHED
Object Keith Huntley
Keith Huntley is an individual notable enough to be recognized as a bearer of the surname Huntley, though specific widely known public details about him are not readily available.
E1899606 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: Keith Huntley | Statement: [Huntley, hasNotableBearer, Keith Huntley]
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: Keith Huntley
Triple: [Huntley, hasNotableBearer, Keith Huntley]
Generated description
Keith Huntley is an individual notable enough to be recognized as a bearer of the surname Huntley, though specific widely known public details about him are not readily available.

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_69f2245f1cf88190978c70d1a1d2cb73 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f677007d808190b5b59f62e21b77cf completed May 2, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2743016cc88190bed1c21d32dac7de completed June 8, 2026, 10:32 p.m.
NEDg Description generation batch_6a2744b316508190b4c0cc56a6d58abb completed June 8, 2026, 10:39 p.m.
NED2 Entity disambiguation (via description) batch_6a27452c57f48190a98dcdfe0c5b2744 completed June 8, 2026, 10:41 p.m.
Created at: April 29, 2026, 6:02 p.m.