Triple
T14951075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weimarer Land |
E372793
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Ilm |
E483016
|
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: Ilm | Statement: [Weimarer Land, locatedOnRiver, Ilm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ilm Context triple: [Weimarer Land, locatedOnRiver, Ilm]
-
A.
Ilm
chosen
The Ilm is a river in the German state of Thuringia that flows through the historic city of Weimar and is known for its picturesque landscapes and cultural associations.
-
B.
Ilm
Ilm is a river in Bavaria, Germany, that flows through the district of Pfaffenhofen an der Ilm and is a tributary of the Danube.
-
C.
Elmi
Elmi is a diminutive form of the given name Elmira, often used as an affectionate nickname.
-
D.
Ilm-Kreis
Ilm-Kreis is a rural district in the state of Thuringia in central Germany, known for its mix of historic towns and forested landscapes in the Thuringian Forest region.
-
E.
Ilami
Ilami is a regional variety of Southern Kurdish spoken primarily in and around the city of Ilam in western Iran.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded690f2e08190ad9dad6dc05a164a |
completed | April 15, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e9a6098819087b6e81bebcf6805 |
completed | May 9, 2026, 12:23 a.m. |
Created at: April 10, 2026, 2:39 a.m.