Triple

T17900307
Position Surface form Disambiguated ID Type / Status
Subject Lobau Island E447553 entity
Predicate locatedNear P294 FINISHED
Object Aspern NE NERFINISHED

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: [Lobau Island, locatedNear, Aspern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aspern
Context triple: [Lobau Island, locatedNear, 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 (2 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_69d8b9f59bd48190a6fc925a855b8bac completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49d8321bc8190a3f679d96323cbbb completed April 19, 2026, 9:16 a.m.
Created at: April 10, 2026, 10:19 a.m.