Triple

T37743259
Position Surface form Disambiguated ID Type / Status
Subject Henriksen E940776 entity
Predicate hasNotableBearer P458 FINISHED
Object Thomas Henriksen
Thomas Henriksen is a relatively obscure individual whose primary distinguishing feature is sharing the surname Henriksen, with no widely recognized public achievements or roles documented.
E2281978 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: Thomas Henriksen | Statement: [Henriksen, hasNotableBearer, Thomas Henriksen]
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: Thomas Henriksen
Triple: [Henriksen, hasNotableBearer, Thomas Henriksen]
Generated description
Thomas Henriksen is a relatively obscure individual whose primary distinguishing feature is sharing the surname Henriksen, with no widely recognized public achievements or roles 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_69f76ee0e32c8190b40a3b4cf590337c completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaec03e5c8190b2408d31a3ad5d1e completed May 6, 2026, 9:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a420df0e96c8190af4ac9e78ddb24f8 completed June 29, 2026, 6:17 a.m.
NEDg Description generation batch_6a420e962d948190ae48e6e87e19a82a completed June 29, 2026, 6:20 a.m.
NED2 Entity disambiguation (via description) batch_6a420f4106fc819089d72df446df93a2 completed June 29, 2026, 6:22 a.m.
Created at: May 3, 2026, 4:18 p.m.