Triple
T5318228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rycken |
E121603
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Rijcken(s)z |
E510216
|
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: Rijcken(s)z | Statement: [Rycken, hasVariantSpelling, Rijcken(s)z]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rijcken(s)z Context triple: [Rycken, hasVariantSpelling, Rijcken(s)z]
-
A.
Rijcken
chosen
Rijcken is a Dutch surname, historically borne by several notable figures in the Netherlands.
-
B.
Gilze en Rijen
Gilze en Rijen is a municipality and town in the southern Netherlands known for its proximity to Breda and its military air base.
-
C.
Rumbartus van Rijn
Rumbartus van Rijn was a member of the van Rijn family, historically associated with the lineage of the Dutch painter Rembrandt van Rijn.
-
D.
Blokzijl
Blokzijl is a historic former trading town and harbor in the Dutch province of Overijssel, known for its picturesque canals and well-preserved old center.
-
E.
Rozenburg
Rozenburg is a town in the western Netherlands that forms part of the heavily industrialized and port-dominated region of South Holland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd855269ac8190bb7a9248d04f1823 |
completed | March 20, 2026, 5:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21b8692881908f04d8cfd7d3d10d |
completed | March 21, 2026, 10:54 p.m. |
Created at: March 20, 2026, 1:59 p.m.