Triple

T20499016
Position Surface form Disambiguated ID Type / Status
Subject Triesenberg E503251 entity
Predicate sharesBorderWith P224 FINISHED
Object Triesen 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: Triesen | Statement: [Triesenberg, sharesBorderWith, Triesen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Triesen
Context triple: [Triesenberg, sharesBorderWith, Triesen]
  • A. Triesen chosen
    Triesen is a municipality in the southern part of Liechtenstein, known for its historic village center and scenic Alpine surroundings.
  • B. Trappstadt
    Trappstadt is a small municipality in the district of Rhön-Grabfeld in northern Bavaria, Germany, known for its rural character and proximity to the Rhön Mountains.
  • C. Trostberg
    Trostberg is a small Bavarian town in southeastern Germany known for its historic old town and chemical industry.
  • D. Wörth
    Wörth is the historical name of Roseninsel, a small, culturally significant island in Lake Starnberg in Bavaria, Germany.
  • E. Rottweil
    Rottweil is a historic town in southwestern Germany known for its medieval architecture and as the namesake of the Rottweiler dog breed.
  • 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_69e0b4b1e52c8190894281cf7e3283ab completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69cbff210819089900e9a35911f48 completed April 20, 2026, 9:38 p.m.
Created at: April 16, 2026, 11:35 a.m.