Triple

T8967110
Position Surface form Disambiguated ID Type / Status
Subject Neisse Viaduct E214165 entity
Predicate connects P390 FINISHED
Object Görlitz E32852 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: Görlitz | Statement: [Neisse Viaduct, connects, Görlitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Görlitz
Context triple: [Neisse Viaduct, connects, Görlitz]
  • A. Görlitz chosen
    Görlitz is a historic city in eastern Germany on the Lusatian Neisse River, known for its well-preserved old town and role as a popular film location.
  • B. Zittau
    Zittau is a historic town in the southeastern corner of Germany, known for its proximity to both the Czech and Polish borders and its well-preserved medieval architecture.
  • C. Bautzen
    Bautzen is a historic town in eastern Germany known for its well-preserved medieval architecture and as a cultural center of the Sorbian minority.
  • D. Liebenwalde
    Liebenwalde is a small town and municipality in the Oberhavel district of the German state of Brandenburg.
  • E. Frankfurt (Oder)
    Frankfurt (Oder) is a German city on the Oder River at the Polish border, known as a historic university and trade center in the state of Brandenburg.
  • 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_69ca839cd6008190a1546a701a56710c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc676389948190aa78fdf6a5ae74a5 completed April 1, 2026, 12:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69d14bb716cc819096a1e02e61db2e69 completed April 4, 2026, 5:34 p.m.
Created at: March 30, 2026, 7:01 p.m.