Triple
T4233000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinsius |
E94624
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Heynsius |
E94624
|
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: Heynsius | Statement: [Heinsius, hasVariant, Heynsius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heynsius Context triple: [Heinsius, hasVariant, Heynsius]
-
A.
Heinsius
chosen
Heinsius is a Dutch surname most notably associated with Anthonie Heinsius, a prominent statesman of the Dutch Republic in the late 17th and early 18th centuries.
-
B.
Hein
Hein is a Dutch surname most notably borne by Piet Hein, a renowned 17th-century naval officer and folk hero of the Dutch Republic.
-
C.
Wolthusen
Wolthusen is a district of the seaport city of Emden in Lower Saxony, Germany, known for its residential character and proximity to the Ems estuary.
-
D.
Sjaalman
Sjaalman is a fictional character in Multatuli’s novel "Max Havelaar," serving as an alter ego and narrative device to expose colonial abuses in the Dutch East Indies.
-
E.
Ozinga
Ozinga is a Dutch surname most notably associated with individuals such as Sjoukje Ozinga.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e65720c819087c4022c774ff7c3 |
completed | March 12, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b596516fd88190b8497ccc7efc7f49 |
completed | March 14, 2026, 5:09 p.m. |
Created at: March 12, 2026, 11:05 p.m.