Triple

T16256664
Position Surface form Disambiguated ID Type / Status
Subject Regierungsbezirk Mittelfranken E394647 entity
Predicate contains P35 FINISHED
Object Schwabach E110122 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: Schwabach | Statement: [Regierungsbezirk Mittelfranken, contains, Schwabach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schwabach
Context triple: [Regierungsbezirk Mittelfranken, contains, Schwabach]
  • A. Schwabach chosen
    Schwabach is a historic town in northern Bavaria, Germany, known for its traditional gold-beating craft and well-preserved old town.
  • B. Schwarzbach
    Schwarzbach is a river in southwestern Germany that flows through the town of Zweibrücken in the state of Rhineland-Palatinate.
  • C. Gaisbach
    Gaisbach is a village and district of the town of Oberkirch in the state of Baden-Württemberg in southwestern Germany.
  • D. Starkenbach
    Starkenbach is a small settlement in the Swiss municipality of Alt St. Johann, located in the canton of St. Gallen.
  • E. Karlinbach
    Karlinbach is a stream in South Tyrol, northern Italy, that serves as one of the inflowing watercourses to Lake Resia in the Alpine region.
  • 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_69d87f221d8081909b0b2063e7528ba2 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2459b1624819086bf681075097235 completed April 17, 2026, 2:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a004f3bd07c81909612f641796deef7 completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:04 a.m.