Triple
T3753306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nieuwkoop |
E81382
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object |
Zevenhoven
Zevenhoven is a village in the Dutch province of South Holland, located within the municipality of Nieuwkoop.
|
E775528
|
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: Zevenhoven | Statement: [Nieuwkoop, hasSettlement, Zevenhoven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zevenhoven Context triple: [Nieuwkoop, hasSettlement, Zevenhoven]
-
A.
Veldhoven
Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
-
B.
Schoonhoven
Schoonhoven is a historic Dutch town in South Holland, renowned for its silver craftsmanship and picturesque riverside setting.
-
C.
Zevenhuizen
Zevenhuizen is a village in the Dutch province of Groningen, located within the municipality of Westerkwartier.
-
D.
Vollenhove
Vollenhove is a historic town in the Dutch province of Overijssel, known for its former status as a regional administrative and noble center with several notable estates and churches.
-
E.
Zeevang
Zeevang is a rural municipality in North Holland, Netherlands, characterized by its polder landscapes and traditional Dutch villages within the greater Amsterdam region.
- 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: Zevenhoven Triple: [Nieuwkoop, hasSettlement, Zevenhoven]
Generated description
Zevenhoven is a village in the Dutch province of South Holland, located within the municipality of Nieuwkoop.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Zevenhoven Target entity description: Zevenhoven is a village in the Dutch province of South Holland, located within the municipality of Nieuwkoop.
-
A.
Veldhoven
Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
-
B.
Schoonhoven
Schoonhoven is a historic Dutch town in South Holland, renowned for its silver craftsmanship and picturesque riverside setting.
-
C.
Zevenhuizen
Zevenhuizen is a village in the Dutch province of Groningen, located within the municipality of Westerkwartier.
-
D.
Vollenhove
Vollenhove is a historic town in the Dutch province of Overijssel, known for its former status as a regional administrative and noble center with several notable estates and churches.
-
E.
Zeevang
Zeevang is a rural municipality in North Holland, Netherlands, characterized by its polder landscapes and traditional Dutch villages within the greater Amsterdam region.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb9340e0819083215989718b4598 |
completed | March 8, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffd37b54881908c67d5746f9ef39e |
completed | April 3, 2026, 5:47 p.m. |
| NEDg | Description generation | batch_69cfff51b8c0819093b2c348fd7819fe |
completed | April 3, 2026, 5:56 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d0014b9c108190b4abe8c974677d31 |
completed | April 3, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:35 p.m.