Triple

T10441522
Position Surface form Disambiguated ID Type / Status
Subject Baden bei Wien E246180 entity
Predicate hasName P744 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: [Baden bei Wien, hasName, Baden bei Wien]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baden bei Wien
Context triple: [Baden bei Wien, hasName, 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. Lenzburg
    Lenzburg is a historic Swiss town in the canton of Aargau, known for its medieval hilltop castle and well-preserved old town.
  • C. Wiener Neustadt
    Wiener Neustadt is a historic city in Lower Austria known as a former imperial residence and military stronghold south of Vienna.
  • D. 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.
  • E. 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.
  • 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_69d381c04fe08190957c26c526a3b05a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4fb9ebf488190ae776bd65e94cb00 completed April 7, 2026, 12:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69d96b2803d88190ab93dd19b4cfee30 completed April 10, 2026, 9:27 p.m.
Created at: April 6, 2026, 12:15 p.m.