Triple
T18760660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geldern |
E458759
|
entity |
| Predicate | hasRiverNearby |
P8567
|
FINISHED |
| Object | Niers |
E138689
|
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: Niers | Statement: [Geldern, hasRiverNearby, Niers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Niers Context triple: [Geldern, hasRiverNearby, Niers]
-
A.
Niers
chosen
The Niers is a small river in western Germany and the southeastern Netherlands that flows through North Rhine-Westphalia before joining the Meuse (Maas).
-
B.
Nieste
Nieste is a small settlement located within Germany's historic Westphalia region.
-
C.
Breyten
Breyten is the given name of Breyten Breytenbach, the renowned South African poet, painter, and anti-apartheid activist.
-
D.
Norriss
Norriss is a variant spelling of the surname Norris, which is of English origin and historically associated with the meaning "northerner" or "from the north."
-
E.
Erwitte
Erwitte is a small town in the German state of North Rhine-Westphalia, known for its historic architecture and location in the Soest district.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d7ecca881909d6c262837b621b3 |
completed | April 20, 2026, 2:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a053d3e4f048190b72ec4ed1dec6c55 |
completed | May 14, 2026, 3:10 a.m. |
Created at: April 10, 2026, 11:52 a.m.