Triple
T6560720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krimpenerwaard |
E152574
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object |
Lekkerkerk
Lekkerkerk is a village in the Dutch province of South Holland, situated along the River Lek and known for its historic dike-side settlement and past environmental contamination case.
|
E658933
|
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: Lekkerkerk | Statement: [Krimpenerwaard, containsSettlement, Lekkerkerk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lekkerkerk Context triple: [Krimpenerwaard, containsSettlement, Lekkerkerk]
-
A.
Ouderkerk
Ouderkerk was a former Dutch municipality in the province of South Holland that later became part of the municipality of Krimpenerwaard.
-
B.
Nieuwerkerken
Nieuwerkerken is a municipality in the Belgian province of Limburg, known for its rural character and small village communities.
-
C.
Nieuwerkerk
Nieuwerkerk is a village in the Dutch province of Zeeland, located on the island and municipality of Schouwen-Duiveland.
-
D.
Grijpskerke
Grijpskerke is a village in the Dutch province of Zeeland, located on the former island of Walcheren.
-
E.
Ridderkerk
Ridderkerk is a town and municipality in the western Netherlands, situated near Rotterdam in the province of South Holland.
- 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: Lekkerkerk Triple: [Krimpenerwaard, containsSettlement, Lekkerkerk]
Generated description
Lekkerkerk is a village in the Dutch province of South Holland, situated along the River Lek and known for its historic dike-side settlement and past environmental contamination case.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lekkerkerk Target entity description: Lekkerkerk is a village in the Dutch province of South Holland, situated along the River Lek and known for its historic dike-side settlement and past environmental contamination case.
-
A.
Ouderkerk
Ouderkerk was a former Dutch municipality in the province of South Holland that later became part of the municipality of Krimpenerwaard.
-
B.
Nieuwerkerken
Nieuwerkerken is a municipality in the Belgian province of Limburg, known for its rural character and small village communities.
-
C.
Nieuwerkerk
Nieuwerkerk is a village in the Dutch province of Zeeland, located on the island and municipality of Schouwen-Duiveland.
-
D.
Grijpskerke
Grijpskerke is a village in the Dutch province of Zeeland, located on the former island of Walcheren.
-
E.
Ridderkerk
Ridderkerk is a town and municipality in the western Netherlands, situated near Rotterdam in the province of South Holland.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae37a5b0819091692fc5def270b9 |
completed | March 27, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7fa57aa9c819081d4ec62bf18d971 |
completed | March 28, 2026, 3:57 p.m. |
| NEDg | Description generation | batch_69c7fbafa2a08190bcfc407d1a6c0d2b |
completed | March 28, 2026, 4:02 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c7fc14691481909d8d029c5c42cd14 |
completed | March 28, 2026, 4:04 p.m. |
Created at: March 27, 2026, 1:52 p.m.