Triple
T14368106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lek |
E356286
|
entity |
| Predicate | confluenceWith |
P2416
|
FINISHED |
| Object | Noord |
E138435
|
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: Noord | Statement: [River Lek, confluenceWith, Noord]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Noord Context triple: [River Lek, confluenceWith, Noord]
-
A.
Noord
chosen
Noord is a major river in the western Netherlands that forms part of the Rhine–Meuse–Scheldt delta and serves as an important waterway for regional shipping and transport.
-
B.
Noord
Noord is the northern terminus station of Amsterdam’s North–South metro line (Line 52), serving as a key public transport hub for the city’s northern districts.
-
C.
Noord
Noord is a residential neighborhood located in the Dutch city of Tilburg.
-
D.
Zuid
Zuid is a major Amsterdam railway and metro station that serves as a key transport hub in the city’s southern business district.
-
E.
Nienoord
Nienoord is a historic Dutch estate and former noble manor known for its stately house, gardens, and heritage attractions in the province of Groningen.
- 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.