Triple

T9589205
Position Surface form Disambiguated ID Type / Status
Subject Rudolfsheim E231372 entity
Predicate belongsToNUTS2Region P9956 FINISHED
Object AT13 (Wien) E536988 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: AT13 (Wien) | Statement: [Rudolfsheim, belongsToNUTS2Region, AT13 (Wien)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AT13 (Wien)
Context triple: [Rudolfsheim, belongsToNUTS2Region, AT13 (Wien)]
  • A. AT1 Eastern Austria chosen
    AT1 Eastern Austria is a NUTS-1 statistical region of Austria that encompasses the country’s eastern federal states for European Union regional analysis and planning.
  • B. Seibersdorf
    Seibersdorf is an Austrian town known for hosting major research and testing laboratories of the International Atomic Energy Agency.
  • C. Krailling
    Krailling is a municipality in the district of Starnberg in Bavaria, Germany, known as a residential community within the Munich metropolitan area.
  • D. Schwechat
    Schwechat is an Austrian town just southeast of Vienna, best known as the site of Vienna International Airport and a major hub for industry and transport.
  • E. Pfersdorf
    Pfersdorf is a village-level subdivision of the municipality of Roth 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_69ca848161688190a68d514a0a9d5129 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd99f1696c8190addf1a43544f2c18 completed April 1, 2026, 10:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69d161880adc819090a9be75ba2a1642 completed April 4, 2026, 7:07 p.m.
Created at: March 30, 2026, 8:06 p.m.