Triple

T7212508
Position Surface form Disambiguated ID Type / Status
Subject Bezirk Schwerin E149439 entity
Predicate hadUrbanDistrict P38406 FINISHED
Object Schwerin E138060 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: Schwerin | Statement: [Bezirk Schwerin, hadUrbanDistrict, Schwerin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schwerin
Context triple: [Bezirk Schwerin, hadUrbanDistrict, Schwerin]
  • A. Schwerin chosen
    Schwerin is a historic city in northern Germany known for its picturesque lakeside setting and landmark Schwerin Castle.
  • B. Neubrandenburg
    Neubrandenburg is a historic city in northeastern Germany known for its well-preserved medieval brick Gothic architecture and distinctive city wall with multiple gate towers.
  • C. 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.
  • D. Mecklenburg-Schwerin
    Mecklenburg-Schwerin was a historical ducal (later grand ducal) state in northern Germany, centered around the city of Schwerin and ruled by the House of Mecklenburg.
  • E. Wismar
    Wismar is a historic Hanseatic port city on Germany’s Baltic Sea coast, known for its well-preserved medieval architecture and UNESCO-listed old town.
  • 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_69c687eca814819095abb52316b1af80 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e98b61448190add3624a818fdc7b completed March 27, 2026, 8:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81eaf59988190a656dae4e588c496 completed March 28, 2026, 6:32 p.m.
Created at: March 27, 2026, 2:53 p.m.