Triple

T23743235
Position Surface form Disambiguated ID Type / Status
Subject Picken E586742 entity
Predicate hasNotableBearer P458 FINISHED
Object David Picken
David Picken is an individual notable enough to be recognized as a namesake of the surname Picken, though specific widely known achievements or roles are not clearly documented.
E1604415 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: David Picken | Statement: [Picken, hasNotableBearer, David Picken]
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: David Picken
Triple: [Picken, hasNotableBearer, David Picken]
Generated description
David Picken is an individual notable enough to be recognized as a namesake of the surname Picken, though specific widely known achievements or roles are not clearly documented.

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_69e24908efb08190bf755c3a9b91f222 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bcbbcf988190b56d74af4b126bd8 completed April 29, 2026, 8:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f696b2bf08190b6cfc375ca7d5e79 completed May 21, 2026, 8:22 p.m.
NEDg Description generation batch_6a0f6d3de27c8190b3cab02a1dfce6ae completed May 21, 2026, 8:38 p.m.
NED2 Entity disambiguation (via description) batch_6a0f6e22305081909ad33dfaf65f004e completed May 21, 2026, 8:42 p.m.
Created at: April 17, 2026, 7:12 p.m.