Triple

T15937027
Position Surface form Disambiguated ID Type / Status
Subject Donaustadt E386464 entity
Predicate contains P35 FINISHED
Object Aspern E188979 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: Aspern | Statement: [Donaustadt, contains, Aspern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aspern
Context triple: [Donaustadt, contains, Aspern]
  • A. Aspern chosen
    Aspern is a district in Vienna, Austria, historically notable as one of the main sites of the 1809 Battle of Aspern-Essling during the Napoleonic Wars.
  • B. Vöcklabruck
    Vöcklabruck is a small historic town in Upper Austria known as a regional center near the Attersee lake and the foothills of the Alps.
  • C. Baltschieder
    Baltschieder is a small Swiss municipality in the canton of Valais, located in the Upper Valais region of the Alps.
  • D. Penzing
    Penzing is a district in the western part of Vienna, Austria, known for its residential areas, green spaces, and proximity to the Vienna Woods.
  • E. Neuötting
    Neuötting is a small Bavarian town in southeastern Germany known for its historic town center and location near the Austrian border.
  • 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_69ffb5b8121881909b15bf6451d3d3a8 completed May 9, 2026, 10:31 p.m.
Created at: April 10, 2026, 4:53 a.m.