Triple

T9540649
Position Surface form Disambiguated ID Type / Status
Subject Regen (district) E230146 entity
Predicate contains P35 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: [Regen (district), contains, Zwiesel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zwiesel
Context triple: [Regen (district), contains, 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. Wolfratshausen
    Wolfratshausen is a Bavarian town in southern Germany known for its historic old town, riverside setting on the Loisach and Isar, and proximity to Munich and the Alps.
  • 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_69ca847b1b3081908f72bc932c17cc41 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98e695948190ab107fff38c57de7 completed April 1, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69deafff4b8c819099d47b48773c3629 completed April 14, 2026, 9:22 p.m.
Created at: March 30, 2026, 8:01 p.m.