Triple
T20310215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willem Adriaan Rijcken |
E510216
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Rijcken |
—
|
NE NERFINISHED |
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: Rijcken | Statement: [Willem Adriaan Rijcken, familyName, Rijcken]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rijcken Context triple: [Willem Adriaan Rijcken, familyName, Rijcken]
-
A.
Rijcken
chosen
Rijcken is a Dutch surname, historically borne by several notable figures in the Netherlands.
-
B.
Rijkel
Rijkel is a village in the Belgian province of Limburg that forms one of the municipal sections of the city of Borgloon.
-
C.
Goudriaan
Goudriaan is a small village in the Dutch province of South Holland, known for its rural character and historic polder landscape.
-
D.
Jan Kempdorp
Jan Kempdorp is a small agricultural and service town in South Africa’s Northern Cape province.
-
E.
Dirck
Dirck is a Dutch masculine given name historically borne by several notable figures, including artists of the Dutch Golden Age.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677436af88190a046c44fa45b68b4 |
completed | April 20, 2026, 6:58 p.m. |
Created at: April 16, 2026, 11:19 a.m.