Triple
T10588641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollander |
E249923
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Holländer |
E249923
|
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: Holländer | Statement: [Hollander, hasVariant, Holländer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holländer Context triple: [Hollander, hasVariant, Holländer]
-
A.
Rijk
Rijk is a Dutch given name, notably borne by the actor and writer Rijk de Gooyer.
-
B.
Hollander
chosen
Hollander is a surname most prominently associated with English actor Tom Hollander, known for his versatile roles in film, television, and theatre.
-
C.
Great Holland
Great Holland is a small village in Essex, England, situated near the coastal town of Frinton-on-Sea.
-
D.
Oland
Oland is a small Hallig island in the North Frisian archipelago off the coast of Germany, known for its tidal landscape and traditional thatched-roof houses.
-
E.
Gelderlander
Gelderlander is a regional Dutch newspaper based in the province of Gelderland.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d527793c588190bfe3a5261eb7f919 |
completed | April 7, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94b9440548190bff01847a940266b |
completed | April 10, 2026, 7:12 p.m. |
Created at: April 6, 2026, 12:40 p.m.