Triple

T26564433
Position Surface form Disambiguated ID Type / Status
Subject Kelliher E666336 entity
Predicate hasNotableBearer P458 FINISHED
Object Liam Kelliher
Liam Kelliher is an individual notable enough to be recognized as a prominent bearer of the surname Kelliher.
E1762274 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: Liam Kelliher | Statement: [Kelliher, hasNotableBearer, Liam Kelliher]
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: Liam Kelliher
Triple: [Kelliher, hasNotableBearer, Liam Kelliher]
Generated description
Liam Kelliher is an individual notable enough to be recognized as a prominent bearer of the surname Kelliher.

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_69ee9cf7e94481909f0d556b36e43572 completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f6149cc0c88190aadaacfa45a2382e completed May 2, 2026, 3:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12535a16e48190bdfe798f281fd4ec completed May 24, 2026, 1:24 a.m.
NEDg Description generation batch_6a12574c06788190951ce13779ea5ba8 completed May 24, 2026, 1:41 a.m.
NED2 Entity disambiguation (via description) batch_6a125793327881908c67b67f1bdf19e6 completed May 24, 2026, 1:42 a.m.
Created at: April 27, 2026, 1:54 a.m.