Triple

T11486317
Position Surface form Disambiguated ID Type / Status
Subject Ehrenburg Palace E272288 entity
Predicate locatedIn P40 FINISHED
Object Coburg E214909 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: Coburg | Statement: [Ehrenburg Palace, locatedIn, Coburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Coburg
Context triple: [Ehrenburg Palace, locatedIn, Coburg]
  • A. Coburg chosen
    Coburg is a historic town in northern Bavaria, Germany, known for its well-preserved medieval architecture and its former role as the seat of the Duchy of Saxe-Coburg and Gotha.
  • B. Coburg
    Coburg is a suburb in Melbourne, Australia, known for its diverse community, historic architecture, and access to the city via major tram routes.
  • C. Bamberg
    Bamberg is a historic city in northern Bavaria, Germany, renowned for its well-preserved medieval old town and status as a UNESCO World Heritage Site.
  • D. Kronach
    Kronach is a historic town in northern Bavaria, Germany, known for its well-preserved medieval old town and the imposing Rosenberg Fortress.
  • E. Altenburg
    Altenburg is a historic town in eastern Thuringia, Germany, known for its playing-card tradition and as the birthplace of the card game Skat.
  • 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85a1fc9688190aacc2eed64229b79 completed April 10, 2026, 2:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69f6d5e2b0408190866bbe9a3a56928b completed May 3, 2026, 4:58 a.m.
Created at: April 8, 2026, 9:36 p.m.