Triple

T11973057
Position Surface form Disambiguated ID Type / Status
Subject Traunviertel E284967 entity
Predicate contains P35 FINISHED
Object city of Wels E176447 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: city of Wels | Statement: [Traunviertel, contains, city of Wels]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Wels
Context triple: [Traunviertel, contains, city of Wels]
  • A. Wels chosen
    Wels is a historic city in Upper Austria known as a former imperial residence and regional economic center.
  • B. Lenzburg
    Lenzburg is a historic Swiss town in the canton of Aargau, known for its medieval hilltop castle and well-preserved old town.
  • C. Wieden
    Wieden is the 4th municipal district of Vienna, Austria, known for its historic architecture, cultural institutions, and central urban character.
  • D. Salzburg
    Salzburg is a historic Austrian city on the Salzach River, renowned for its baroque architecture, Alpine setting, and as the birthplace of composer Wolfgang Amadeus Mozart.
  • E. St. Pölten
    St. Pölten is the capital city of the Austrian state of Lower Austria, known for its baroque architecture and role as a regional administrative and cultural center.
  • 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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9039107e48190ae4c4efd6257dd3c completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4597cf818819089b0d897c236b87b completed May 1, 2026, 7:42 a.m.
Created at: April 8, 2026, 9:46 p.m.