Triple
T16805412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overasselt |
E408467
|
entity |
| Predicate | locatedInMunicipality |
P40
|
FINISHED |
| Object | Heumen |
E84055
|
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: Heumen | Statement: [Overasselt, locatedInMunicipality, Heumen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heumen Context triple: [Overasselt, locatedInMunicipality, Heumen]
-
A.
Heumen
chosen
Heumen is a small municipality in the province of Gelderland in the eastern Netherlands, located just south of the city of Nijmegen.
-
B.
Hondius
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.
-
C.
De Haan
De Haan is a seaside resort town on the Belgian coast, known for its Belle Époque architecture and beaches.
-
D.
Marheineke
Marheineke is a German surname most notably associated with the 19th-century Protestant theologian Philipp Marheineke.
-
E.
Heezen
Heezen is a surname most notably associated with American geologist and oceanographer Bruce C. Heezen, a pioneer in mapping the ocean floor.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cc25dc81909443b2c83155267a |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b28d3a808190bc94a4f09a10da7e |
completed | May 10, 2026, 4:30 p.m. |
Created at: April 10, 2026, 5:22 a.m.