Triple
T15609343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmold |
E375244
|
entity |
| Predicate | hasRelatedName |
P3889
|
FINISHED |
| Object | Helmwald |
E60853
|
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: Helmwald | Statement: [Helmold, hasRelatedName, Helmwald]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helmwald Context triple: [Helmold, hasRelatedName, Helmwald]
-
A.
Wildenberg
Wildenberg is a small municipality in the Kelheim district of Lower Bavaria, Germany, known for its rural character and agricultural surroundings.
-
B.
Hereweald
chosen
Hereweald is an Old English personal name meaning “army ruler,” from which the later given name Harold is derived.
-
C.
Hohenfurch
Hohenfurch is a small Bavarian municipality in southern Germany, known for its rural character and scenic location near the Alps.
-
D.
Reinswald
Reinswald is a small alpine village and ski resort located in the Sarntal Alps of South Tyrol in northern Italy.
-
E.
Finsterwald
Finsterwald is a forested area or locality that forms part of the Bavarian town of Gmund am Tegernsee in southern Germany.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e8024948190a6c711f2e5c2aac4 |
completed | April 16, 2026, 2:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff56d51c28819097b8c2c0e2307401 |
completed | May 9, 2026, 3:46 p.m. |
Created at: April 10, 2026, 4:13 a.m.