Triple
T15946892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wetzlar |
E386707
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Schladming |
E726350
|
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: Schladming | Statement: [Wetzlar, hasTwinTown, Schladming]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schladming Context triple: [Wetzlar, hasTwinTown, Schladming]
-
A.
Schladming
chosen
Schladming is a renowned Austrian alpine ski resort town in Styria, famous for hosting major international ski races and World Cup events.
-
B.
Oberstdorf
Oberstdorf is a renowned alpine resort town in southern Germany known for skiing, ski jumping, and hiking amid dramatic mountain scenery.
-
C.
Kitzbühel
Kitzbühel is a renowned Austrian alpine town famous for its ski resorts and the annual Hahnenkamm downhill race.
-
D.
Igls
Igls is an Austrian alpine village near Innsbruck known for its winter sports facilities and role in hosting Olympic events.
-
E.
Zell am See
Zell am See is a popular Austrian alpine town and lakeside resort known for its scenic mountain setting, skiing, and outdoor recreation.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156d1a4c08190afc325491ba38870 |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf14ab088190b1d2f1f6b18bf85d |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 4:53 a.m.