Triple

T15330734
Position Surface form Disambiguated ID Type / Status
Subject Linz tramway network E366524 entity
Predicate owner P347 FINISHED
Object Stadt Linz E75219 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: Stadt Linz | Statement: [Linz tramway network, owner, Stadt Linz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stadt Linz
Context triple: [Linz tramway network, owner, Stadt Linz]
  • A. Linz chosen
    Linz is a major Austrian city known for its industrial heritage, vibrant cultural scene, and location along the Danube River.
  • B. 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.
  • C. Wiener Neustadt
    Wiener Neustadt is a historic city in Lower Austria known as a former imperial residence and military stronghold south of Vienna.
  • D. Linz am Rhein
    Linz am Rhein is a historic town on the Rhine River in Rhineland-Palatinate, western Germany, known for its well-preserved medieval old town and colorful half-timbered houses.
  • E. Lenzburg
    Lenzburg is a historic Swiss town in the canton of Aargau, known for its medieval hilltop castle and well-preserved old town.
  • 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_69d85a121520819093dcce999fdefe1a completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e0161ac8190aa1d52c063c02ad0 completed April 16, 2026, 1:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff6ec2f35c8190a96af080cd7b6d0e completed May 9, 2026, 5:28 p.m.
Created at: April 10, 2026, 3:17 a.m.