Triple

T31251673
Position Surface form Disambiguated ID Type / Status
Subject Linder E796837 entity
Predicate hasNotableBearer P458 FINISHED
Object Rolf Linder
Rolf Linder is a person notable enough to be recognized as a bearer of the surname Linder, though specific widely known public details about him are not clearly established.
E2117197 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: Rolf Linder | Statement: [Linder, hasNotableBearer, Rolf Linder]
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: Rolf Linder
Triple: [Linder, hasNotableBearer, Rolf Linder]
Generated description
Rolf Linder is a person notable enough to be recognized as a bearer of the surname Linder, though specific widely known public details about him 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_69f224dc84d0819081f1cb6f9127e6b1 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69d5773e48190b53ad50be1196f16 completed May 3, 2026, 12:56 a.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 29, 2026, 9:11 p.m.