Triple

T1540454
Position Surface form Disambiguated ID Type / Status
Subject Görlitz E32852 entity
Predicate hasRailConnectionTo P848 FINISHED
Object Dresden E37454 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: Dresden | Statement: [Görlitz, hasRailConnectionTo, Dresden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dresden
Context triple: [Görlitz, hasRailConnectionTo, Dresden]
  • A. Dresden
    Dresden is a small community within the municipality of Chatham-Kent in southwestern Ontario, Canada, known historically for its role in the Underground Railroad and Black settlement.
  • B. Dresden chosen
    Dresden is a historic cultural and economic center in eastern Germany, renowned for its baroque architecture, art collections, and reconstruction after World War II.
  • C. Leipzig
    Leipzig is a major city in eastern Germany known for its rich cultural heritage, vibrant music and arts scene, and important role in trade and commerce.
  • D. Chemnitz
    Chemnitz is a city in eastern Germany known for its industrial heritage and post-reunification urban redevelopment.
  • E. Magdeburg
    Magdeburg is a historic city in central Germany, known for its medieval cathedral, role as a major trading and industrial center, and location on the Elbe River.
  • 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_69a885ed29088190a3c2d5a3d100c16e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9083c942481909168394b6674d82b completed March 5, 2026, 4:36 a.m.
NED1 Entity disambiguation (via context triple) batch_69afce6ea6f88190b455439f73a02728 completed March 10, 2026, 7:55 a.m.
Created at: March 4, 2026, 7:26 p.m.