Triple

T28135157
Position Surface form Disambiguated ID Type / Status
Subject Shaffer E714178 entity
Predicate hasNotableBearer P458 FINISHED
Object Lynn Shaffer
Lynn Shaffer is an individual notable enough to be recognized as a bearer of the surname Shaffer, though specific widely known public details about her are not clearly established.
E2117170 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: Lynn Shaffer | Statement: [Shaffer, hasNotableBearer, Lynn Shaffer]
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: Lynn Shaffer
Triple: [Shaffer, hasNotableBearer, Lynn Shaffer]
Generated description
Lynn Shaffer is an individual notable enough to be recognized as a bearer of the surname Shaffer, though specific widely known public details about her are not clearly established.

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_69efd6af156c81908f50c2cd7db0e1ef completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f6412eece8819083585f8d75aff17d completed May 2, 2026, 6:23 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3786b1cf408190a05ec092820cb539 completed June 21, 2026, 6:37 a.m.
NEDg Description generation batch_6a378f7c14f881908b059b59ec6c892b completed June 21, 2026, 7:15 a.m.
NED2 Entity disambiguation (via description) batch_6a37900b238c8190bda9ac2ff1af848e completed June 21, 2026, 7:17 a.m.
Created at: April 27, 2026, 9:49 p.m.