Triple

T9071289
Position Surface form Disambiguated ID Type / Status
Subject Bezirk Baden E217371 entity
Predicate administrativeCenter P1474 FINISHED
Object Baden bei Wien E246180 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: Baden bei Wien | Statement: [Bezirk Baden, administrativeCenter, Baden bei Wien]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baden bei Wien
Context triple: [Bezirk Baden, administrativeCenter, Baden bei Wien]
  • A. Baden bei Wien chosen
    Baden bei Wien is a historic spa town in eastern Austria renowned for its thermal springs, Biedermeier architecture, and proximity to Vienna.
  • B. Wiener Neustadt
    Wiener Neustadt is a historic city in Lower Austria known as a former imperial residence and military stronghold south of Vienna.
  • C. Tulln an der Donau
    Tulln an der Donau is an Austrian town on the Danube River, known for its rich history and as the birthplace of painter Egon Schiele.
  • D. St. Pölten
    St. Pölten is the capital city of the Austrian state of Lower Austria, known for its baroque architecture and role as a regional administrative and cultural center.
  • E. Linz
    Linz is a major Austrian city known for its industrial heritage, vibrant cultural scene, and location along the Danube River.
  • 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_69ca83d5a7f48190b16c1e59bd43ede0 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc955ec5c0819089bb42448edf391e completed April 1, 2026, 3:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05beac7a08190a4e7634bf02ce304 completed April 4, 2026, 12:31 a.m.
Created at: March 30, 2026, 7:12 p.m.