Triple
T14368121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lek |
E356286
|
entity |
| Predicate | separates |
P1175
|
FINISHED |
| Object | Vijfheerenlanden |
E353847
|
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: Vijfheerenlanden | Statement: [River Lek, separates, Vijfheerenlanden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vijfheerenlanden Context triple: [River Lek, separates, Vijfheerenlanden]
-
A.
Vijfheerenlanden
chosen
Vijfheerenlanden is a historical region in the Netherlands known for its polder landscape and long-standing water management traditions along the Lek River.
-
B.
Mijnsheerenland
Mijnsheerenland is a village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
-
C.
Koedijkslanden
Koedijkslanden is a residential district in the Dutch city of Meppel, known for its suburban housing and local amenities.
-
D.
Rietlanden
Rietlanden is a waterfront area in Amsterdam’s Eastern Docklands, known for its former industrial port functions and subsequent urban redevelopment.
-
E.
Foosland
Foosland is a small village located in Champaign County, Illinois, United States.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8faf00e8819087d7100e9d8c1877 |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c51bf888190b1776461884c4514 |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:15 a.m.