Triple
T15875824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elsenz |
E384950
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Elsenz (German) |
E384950
|
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: Elsenz (German) | Statement: [Elsenz, hasNameInLanguage, Elsenz (German)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elsenz (German) Context triple: [Elsenz, hasNameInLanguage, Elsenz (German)]
-
A.
Iller (German)
Iller (German) is the German name for the Iller River, a tributary of the Danube in southern Germany.
-
B.
Alt-Lichtenberg (German)
Alt-Lichtenberg (German) is the German name for the Alt-Lichtenberg locality, a district-level area within the Berlin borough of Lichtenberg.
-
C.
Elend (German)
Elend (German) is the German term for "misery," denoting a state of great suffering, distress, or hardship.
-
D.
Sinn (German)
Sinn (German) is the term used by philosopher Gottlob Frege to denote the "sense" or mode of presentation of a linguistic expression, distinguishing it from its reference (Bedeutung).
-
E.
Elsenz
chosen
The Elsenz is a river in southwestern Germany that flows through the Kraichgau region before joining the Neckar.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e155fcffbc8190ba6d133107b83a7f |
completed | April 16, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa94e9b548190bec74e6d9790d241 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:51 a.m.