Triple
T4045500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heumen |
E84055
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object |
Heumen (village)
Heumen (village) is a small Dutch village in the province of Gelderland, serving as the namesake and administrative center of the municipality of Heumen.
|
E408468
|
NE FINISHED |
How this triple was built (4 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 (village) | Statement: [Heumen, hasSettlement, Heumen (village)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heumen (village) Context triple: [Heumen, hasSettlement, Heumen (village)]
-
A.
Zevenhuizen
Zevenhuizen is a village in the Dutch province of Groningen, located within the municipality of Westerkwartier.
-
B.
Heusden
Heusden is a historic fortified town in the southern Netherlands known for its well-preserved ramparts and picturesque old harbor.
-
C.
Bunschoten
Bunschoten is a Dutch town and municipality known for its traditional fishing heritage and historic village character in the central Netherlands.
-
D.
Holendrecht
Holendrecht is a metro station in Amsterdam serving the southeastern part of the city, including the nearby academic hospital and university campus.
-
E.
Ommelanderwijk
Ommelanderwijk is a village in the municipality of Veendam in the province of Groningen in the northeastern Netherlands.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Heumen (village) Triple: [Heumen, hasSettlement, Heumen (village)]
Generated description
Heumen (village) is a small Dutch village in the province of Gelderland, serving as the namesake and administrative center of the municipality of Heumen.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Heumen (village) Target entity description: Heumen (village) is a small Dutch village in the province of Gelderland, serving as the namesake and administrative center of the municipality of Heumen.
-
A.
Zevenhuizen
Zevenhuizen is a village in the Dutch province of Groningen, located within the municipality of Westerkwartier.
-
B.
Heusden
Heusden is a historic fortified town in the southern Netherlands known for its well-preserved ramparts and picturesque old harbor.
-
C.
Bunschoten
Bunschoten is a Dutch town and municipality known for its traditional fishing heritage and historic village character in the central Netherlands.
-
D.
Holendrecht
Holendrecht is a metro station in Amsterdam serving the southeastern part of the city, including the nearby academic hospital and university campus.
-
E.
Ommelanderwijk
Ommelanderwijk is a village in the municipality of Veendam in the province of Groningen in the northeastern Netherlands.
- F. None of above. chosen
Provenance (5 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb5f85d48190ba80a0a24fbe438a |
completed | March 9, 2026, 4:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b55652228c8190a9f301676deb0055 |
completed | March 14, 2026, 12:36 p.m. |
| NEDg | Description generation | batch_69b556fec4708190b221893ec35f1a38 |
completed | March 14, 2026, 12:39 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b557f73cbc8190b904089ab0fa97d6 |
completed | March 14, 2026, 12:43 p.m. |
Created at: March 9, 2026, 3:37 p.m.