Triple
T15481436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lidzbark Warmiński |
E376926
|
entity |
| Predicate | hasGermanName |
P1435
|
FINISHED |
| Object | Heilsberg |
E751943
|
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: Heilsberg | Statement: [Lidzbark Warmiński, hasGermanName, Heilsberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heilsberg Context triple: [Lidzbark Warmiński, hasGermanName, Heilsberg]
-
A.
Heilsberg
chosen
Heilsberg is a historic town in northeastern Poland, known today as Lidzbark Warmiński, that was the site of significant medieval and Napoleonic-era military engagements.
-
B.
Ranselberg
Ranselberg is a locality or district that forms part of the town of Lorch in Germany.
-
C.
Hesselberg
Hesselberg is a prominent hill in Bavaria, Germany, known as the highest elevation of the Franconian Alb region.
-
D.
Ölberg
Ölberg is the highest and one of the most prominent hills in Germany’s Siebengebirge range, known for its scenic views over the Rhine Valley.
-
E.
Voitsberg
Voitsberg is a small town in southeastern Austria known for its industrial heritage and location within the federal state of Styria.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8cb4388190a3b4c92c3bb4ad4f |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d0d6ef0819091623de2888a7101 |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:34 a.m.