Triple

T21414136
Position Surface form Disambiguated ID Type / Status
Subject Dukes of Pomerania E528254 entity
Predicate capital P234 FINISHED
Object Stolp NE NERFINISHED

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: Stolp | Statement: [Dukes of Pomerania, capital, Stolp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stolp
Context triple: [Dukes of Pomerania, capital, Stolp]
  • A. Stolp chosen
    Stolp is the historical German name for the Polish city of Słupsk, a regional center in northern Poland near the Baltic coast.
  • B. Stargard
    Stargard is a town in northwestern Poland known for its medieval architecture and historical role as a strategic military and administrative center.
  • C. Biebrich
    Biebrich is a district of Wiesbaden in the German state of Hesse, historically known as an independent town on the Rhine and the site of the Baroque Biebrich Palace.
  • D. Görlitz
    Görlitz is a historic city in eastern Germany on the Lusatian Neisse River, known for its well-preserved old town and role as a popular film location.
  • E. Küstrin
    Küstrin is a historic town on the Oder River—now largely part of Kostrzyn nad Odrą in western Poland—that once belonged to Germany and served as a significant Prussian fortress and administrative center.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b2032fe48190907b282e2fffa2bd completed April 22, 2026, 11:33 a.m.
Created at: April 16, 2026, 5:44 p.m.