Triple

T12429064
Position Surface form Disambiguated ID Type / Status
Subject Stannern E296976 entity
Predicate hasGermanName P1435 FINISHED
Object Stannern E296976 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: Stannern | Statement: [Stannern, hasGermanName, Stannern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stannern
Context triple: [Stannern, hasGermanName, Stannern]
  • A. Stannern chosen
    Stannern is a village in the Czech Republic (now known as Stonařov) historically notable as the birthplace of Austrian Nazi politician Arthur Seyss-Inquart.
  • B. Störnstein
    Störnstein is a small municipality in the Upper Palatinate region of Bavaria, Germany.
  • C. Radenthein
    Radenthein is a small town in the Austrian state of Carinthia, known for its alpine setting and history of magnesite mining.
  • D. Pottenstein
    Pottenstein is a small town in Lower Austria known for its scenic surroundings and traditional Austrian character.
  • E. Stupava
    Stupava is a small town in western Slovakia known for its historic center, cultural festivals, and proximity to the capital city of Bratislava.
  • 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_69d6ada0640c81908c061d7fb3d47786 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d7ddc688190bddb242d67fa6e89 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64b9aaf9c819098e8f8ba40c73363 completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:55 p.m.