Triple
T18710777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jodocus Hondius |
E457505
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hondius |
—
|
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: Hondius | Statement: [Jodocus Hondius, familyName, Hondius]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hondius Context triple: [Jodocus Hondius, familyName, Hondius]
-
A.
Hondius
chosen
Hondius is a Dutch family name most famously associated with Jodocus Hondius, a prominent 16th–17th century cartographer and engraver known for his influential maps and atlases.
-
B.
Hoornaar
Hoornaar is a village in the Dutch province of South Holland, known for its rural character and traditional polder landscape.
-
C.
Bredius
Bredius is a Dutch surname most notably associated with Abraham Bredius, a prominent art historian and expert on Dutch Golden Age painting.
-
D.
Poulus
Poulus is a personal name variant derived from the given name Poul.
-
E.
Heumen
Heumen is a small municipality in the province of Gelderland in the eastern Netherlands, located just south of the city of Nijmegen.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671b34508190b6180f7d6ad50a58 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 10, 2026, 11:50 a.m.