Triple

T28666148
Position Surface form Disambiguated ID Type / Status
Subject Bowers E725590 entity
Predicate hasNotableBearer P458 FINISHED
Object Norman Bowers
Norman Bowers is a notable individual distinguished enough to be specifically recognized as a bearer of the surname Bowers.
E1861298 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: Norman Bowers | Statement: [Bowers, hasNotableBearer, Norman Bowers]
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: Norman Bowers
Triple: [Bowers, hasNotableBearer, Norman Bowers]
Generated description
Norman Bowers is a notable individual distinguished enough to be specifically recognized as a bearer of the surname Bowers.

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_69f01d85be388190b669a0e401e2f2c4 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f655a43fb4819087b2979884dbd497 completed May 2, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25a834e5e48190b13fbd53b5be3aa3 completed June 7, 2026, 5:19 p.m.
NEDg Description generation batch_6a25ac482b2c8190b29f490879ef6ea6 completed June 7, 2026, 5:37 p.m.
NED2 Entity disambiguation (via description) batch_6a25b03453348190952e1ebd49c800b9 completed June 7, 2026, 5:53 p.m.
Created at: April 28, 2026, 5:01 a.m.