Triple

T12042000
Position Surface form Disambiguated ID Type / Status
Subject Nepomuk E286683 entity
Predicate hasTwinTown P919 FINISHED
Object Zwiesel E871095 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: Zwiesel | Statement: [Nepomuk, hasTwinTown, Zwiesel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zwiesel
Context triple: [Nepomuk, hasTwinTown, Zwiesel]
  • A. Zwiesel chosen
    Zwiesel is a small Bavarian town in southeastern Germany known for its glassmaking tradition and its location on the edge of the Bavarian Forest.
  • B. Zwiesel
    Zwiesel is a prominent mountain in the Bavarian Alps of southeastern Germany, known for its scenic hiking routes and panoramic views over the Bad Reichenhall area.
  • C. Straubing
    Straubing is a Bavarian town on the Danube River known for its historic city center and role as a regional economic and educational hub.
  • D. Donauwörth
    Donauwörth is a historic Bavarian town in southern Germany situated at the confluence of the Danube and Lech rivers.
  • E. Wörth
    Wörth is the historical name of Roseninsel, a small, culturally significant island in Lake Starnberg in Bavaria, 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9040d13108190bd1a969fa62aae5a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7c6f1e29c8190b073c3293cf68cb2 completed May 3, 2026, 10:06 p.m.
Created at: April 8, 2026, 9:47 p.m.