Triple
T21095270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helme River |
E519748
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Helme@de |
—
|
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: Helme@de | Statement: [Helme River, hasNameInLanguage, Helme@de]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helme@de Context triple: [Helme River, hasNameInLanguage, Helme@de]
-
A.
Hamel
Hamel is a surname of French origin borne by various notable individuals across fields such as entertainment, sports, and academia.
-
B.
Hel
Hel is the Norse goddess who rules over the underworld realm of the dead that bears her name.
-
C.
Hel
Hel is a town and popular seaside resort located at the tip of the Hel Peninsula on Poland’s Baltic coast.
-
D.
Helme
Helme is a small village in West Yorkshire, England, situated near Meltham on the edge of the Pennines.
-
E.
Helme
chosen
Helme is a river in central Germany that serves as a tributary of the Unstrut.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5845f88190a16f3df157f0906c |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 2:52 p.m.