Triple

T15937021
Position Surface form Disambiguated ID Type / Status
Subject Donaustadt E386464 entity
Predicate contains P35 FINISHED
Object Donau City E395330 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: Donau City | Statement: [Donaustadt, contains, Donau City]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Donau City
Context triple: [Donaustadt, contains, Donau City]
  • A. Donau City chosen
    Donau City is a modern business and residential district in Vienna known for its high-rise buildings and proximity to the Danube River.
  • B. Budapest
    Budapest is the capital and largest city of Hungary, renowned for its historic architecture, thermal baths, and prominent location along the Danube River.
  • C. Dunaújváros
    Dunaújváros is an industrial city in central Hungary known for its steel production and post-war socialist urban planning.
  • D. Budaörs
    Budaörs is a suburban town near Budapest in Hungary, known for its rapid post-communist development and role as a commercial and residential hub.
  • E. Újbuda
    Újbuda is a major residential and commercial district on the Buda side of Budapest, known for its universities, cultural venues, and riverside areas along the Danube.
  • 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_69d86da750008190987eb26be3f6c118 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156ab7f548190b2d1aafa0e6d2c24 completed April 16, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3bfe72c819095f40a255bcd7ad5 completed May 9, 2026, 11:31 p.m.
Created at: April 10, 2026, 4:53 a.m.