Triple

T24794124
Position Surface form Disambiguated ID Type / Status
Subject de Mol E620330 entity
Predicate hasNotableBearer P458 FINISHED
Object Hendrik de Mol
Hendrik de Mol is a person notable enough to be recognized as a prominent bearer of the surname "de Mol."
E1732365 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: Hendrik de Mol | Statement: [de Mol, hasNotableBearer, Hendrik de Mol]
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: Hendrik de Mol
Triple: [de Mol, hasNotableBearer, Hendrik de Mol]
Generated description
Hendrik de Mol is a person notable enough to be recognized as a prominent bearer of the surname "de Mol."

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_69e2fabe77c8819085f7ce6486248139 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f41105cc388190aba8267b0bf56354 completed May 1, 2026, 2:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11c7dc81888190badc0270f2ddc72b completed May 23, 2026, 3:29 p.m.
NEDg Description generation batch_6a11c9561de8819080cf8940f865fc76 completed May 23, 2026, 3:35 p.m.
NED2 Entity disambiguation (via description) batch_6a11ca2243988190a158631f4b94e205 completed May 23, 2026, 3:39 p.m.
Created at: April 18, 2026, 4:48 a.m.