Triple

T15982133
Position Surface form Disambiguated ID Type / Status
Subject Graz Hauptbahnhof E387600 entity
Predicate hasNativeName P1435 FINISHED
Object Graz Hauptbahnhof E387600 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: Graz Hauptbahnhof | Statement: [Graz Hauptbahnhof, hasNativeName, Graz Hauptbahnhof]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Graz Hauptbahnhof
Context triple: [Graz Hauptbahnhof, hasNativeName, Graz Hauptbahnhof]
  • A. Graz Hauptbahnhof chosen
    Graz Hauptbahnhof is the main railway station and central transport hub of the city of Graz in Austria.
  • B. Wien Hauptbahnhof
    Wien Hauptbahnhof is Vienna’s main railway station and a central national and international transport hub in Austria.
  • C. Linz Central Station
    Linz Central Station is the main railway hub of Linz, Austria, serving as a key regional and long-distance transport interchange.
  • D. Salzburg Hauptbahnhof
    Salzburg Hauptbahnhof is the main railway station in Salzburg, Austria, serving as a major national and international transport hub.
  • E. St. Pölten Hauptbahnhof
    St. Pölten Hauptbahnhof is the main railway station and central transport hub of the city of St. Pölten in Lower Austria, serving regional and long-distance rail connections.
  • 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_69d86da94ccc819083d187f5dc6a123e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e15755b5548190acfa29eecb11e675 completed April 16, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3cb0ed48190b35c19f3961f183b completed May 9, 2026, 11:31 p.m.
Created at: April 10, 2026, 4:54 a.m.