Triple

T26625679
Position Surface form Disambiguated ID Type / Status
Subject Rademakers E668335 entity
Predicate hasNotableBearer P458 FINISHED
Object Paul Rademakers
Paul Rademakers is an individual notable enough to be recognized as a prominent bearer of the surname Rademakers.
E1741286 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: Paul Rademakers | Statement: [Rademakers, hasNotableBearer, Paul Rademakers]
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: Paul Rademakers
Triple: [Rademakers, hasNotableBearer, Paul Rademakers]
Generated description
Paul Rademakers is an individual notable enough to be recognized as a prominent bearer of the surname Rademakers.

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_69ee9cff507c819092b95bf7219a702e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f615e9643881908e03a3eb018d13d2 completed May 2, 2026, 3:19 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12092b1ccc81908e5e214ee43b83db completed May 23, 2026, 8:08 p.m.
NEDg Description generation batch_6a120aa69a8c819083a6dc95e4d6382e completed May 23, 2026, 8:14 p.m.
NED2 Entity disambiguation (via description) batch_6a120b329b30819089e007135e13dc21 completed May 23, 2026, 8:16 p.m.
Created at: April 27, 2026, 2:23 a.m.