Triple

T36574387
Position Surface form Disambiguated ID Type / Status
Subject Lee Felsenstein E902204 entity
Predicate familyName P18 FINISHED
Object Felsenstein
Felsenstein is a surname most notably associated with figures in computing and evolutionary biology, including computer engineer Lee Felsenstein and statistician Joseph Felsenstein.
E2190596 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: Felsenstein | Statement: [Lee Felsenstein, familyName, Felsenstein]
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: Felsenstein
Triple: [Lee Felsenstein, familyName, Felsenstein]
Generated description
Felsenstein is a surname most notably associated with figures in computing and evolutionary biology, including computer engineer Lee Felsenstein and statistician Joseph Felsenstein.

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_69f76e6416708190a9754b8c52d4e453 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c2a3912c8190968c811183d8b8cb completed May 3, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39f90fee288190a45ee9eb3e0fc78d completed June 23, 2026, 3:10 a.m.
NEDg Description generation batch_6a39f9bd44a88190a65d9c6a28cc9836 completed June 23, 2026, 3:13 a.m.
NED2 Entity disambiguation (via description) batch_6a39fcda8cf481908862a0458439039a completed June 23, 2026, 3:26 a.m.
Created at: May 3, 2026, 4:11 p.m.