Triple
T21993278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huisman |
E543140
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Rienk Huisman
Rienk Huisman is a person notable enough to be recognized as a bearer of the Dutch surname Huisman.
|
E1518475
|
NE FINISHED |
How this triple was built (4 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: Rienk Huisman | Statement: [Huisman, hasNotableBearer, Rienk Huisman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rienk Huisman Context triple: [Huisman, hasNotableBearer, Rienk Huisman]
-
A.
Henk Huisman
Henk Huisman is a person notable enough to be recognized as a prominent bearer of the Dutch surname Huisman.
-
B.
Jan Huisman
Jan Huisman is a notable individual who shares the Dutch surname Huisman, recognized among its more prominent bearers.
-
C.
Theo Huisman
Theo Huisman is a person notable enough to be recognized as a prominent bearer of the Dutch surname Huisman.
-
D.
Jeroen Bleekemolen
Jeroen Bleekemolen is a Dutch professional racing driver known for competing in series such as the 24 Hours of Le Mans, DTM, and various GT and endurance championships.
-
E.
Jaap Huisman
Jaap Huisman is a Dutch individual known primarily for bearing the Huisman surname, though no widely recognized public achievements or roles are prominently associated with him.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Rienk Huisman Triple: [Huisman, hasNotableBearer, Rienk Huisman]
Generated description
Rienk Huisman is a person notable enough to be recognized as a bearer of the Dutch surname Huisman.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rienk Huisman Target entity description: Rienk Huisman is a person notable enough to be recognized as a bearer of the Dutch surname Huisman.
-
A.
Henk Huisman
Henk Huisman is a person notable enough to be recognized as a prominent bearer of the Dutch surname Huisman.
-
B.
Jan Huisman
Jan Huisman is a notable individual who shares the Dutch surname Huisman, recognized among its more prominent bearers.
-
C.
Theo Huisman
Theo Huisman is a person notable enough to be recognized as a prominent bearer of the Dutch surname Huisman.
-
D.
Jeroen Bleekemolen
Jeroen Bleekemolen is a Dutch professional racing driver known for competing in series such as the 24 Hours of Le Mans, DTM, and various GT and endurance championships.
-
E.
Jaap Huisman
Jaap Huisman is a Dutch individual known primarily for bearing the Huisman surname, though no widely recognized public achievements or roles are prominently associated with him.
- F. None of above. chosen
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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1270f77fc8190aadcc02760d65ac0 |
completed | April 28, 2026, 9:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0a8789961081908b26980f1dd018d7 |
completed | May 18, 2026, 3:29 a.m. |
| NEDg | Description generation | batch_6a0a89500af08190a4837a0ef6d7042d |
completed | May 18, 2026, 3:36 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0a8a353b3881908230b1dc890c896f |
completed | May 18, 2026, 3:40 a.m. |
Created at: April 16, 2026, 8:15 p.m.