Triple
T20631696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eembrugge |
E506970
|
entity |
| Predicate | locatedOnWatercourse |
P1489
|
FINISHED |
| Object | Eem |
—
|
NE NERFINISHED |
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: Eem | Statement: [Eembrugge, locatedOnWatercourse, Eem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eem Context triple: [Eembrugge, locatedOnWatercourse, Eem]
-
A.
Eem
chosen
The Eem is a small river in the central Netherlands that flows through the city of Amersfoort before emptying into the Eemmeer.
-
B.
Eemvallei
Eemvallei is a low-lying floodplain area in the Netherlands associated with the River Eem, characterized by wetlands and agricultural landscapes.
-
C.
Eemmeer
Eemmeer is a lake in the central Netherlands that forms part of the border between the provinces of Flevoland and Utrecht and is used for recreation and water management.
-
D.
Eemnes
Eemnes is a small town and municipality in the central Netherlands known for its characteristic polder landscape and historic village centers.
-
E.
Ema
Ema is an Austronesian language spoken primarily in East Timor, also known as the Kemak language.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0b0508819093c62a4ceaf860ce |
completed | April 20, 2026, 10:47 p.m. |
Created at: April 16, 2026, 11:42 a.m.