Triple

T10172332
Position Surface form Disambiguated ID Type / Status
Subject Baden District E235360 entity
Predicate contains P35 FINISHED
Object Leobersdorf E787696 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: Leobersdorf | Statement: [Baden District, contains, Leobersdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leobersdorf
Context triple: [Baden District, contains, Leobersdorf]
  • A. Leobersdorf chosen
    Leobersdorf is a market town in Lower Austria known for its wine-growing tradition and location in the Baden district south of Vienna.
  • B. Berndorf
    Berndorf is a small locality in Germany known historically as the birthplace of the pioneering refrigeration engineer Carl von Linde.
  • C. Berndorf
    Berndorf is a small industrial town in Lower Austria known for its historic metalworking industry and characteristic workers’ housing estates.
  • D. Oberwaltersdorf
    Oberwaltersdorf is a municipality in Lower Austria known for its residential character, proximity to Vienna, and local wine-growing and leisure facilities.
  • E. Jägerndorf
    Jägerndorf is a historic Silesian town (now Krnov in the Czech Republic) known for its strategic and political significance in Central European history.
  • 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_69ca84ceafd0819085828600e11bed6b completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdec9f6dd8819081588600499165ee completed April 2, 2026, 4:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69d354fc0a808190aa57b68708d91590 completed April 6, 2026, 6:38 a.m.
Created at: March 30, 2026, 9:10 p.m.