Triple

T4254832
Position Surface form Disambiguated ID Type / Status
Subject Szentendre E95946 entity
Predicate hasTwinTown P919 FINISHED
Object Gniezno E226276 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: Gniezno | Statement: [Szentendre, hasTwinTown, Gniezno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gniezno
Context triple: [Szentendre, hasTwinTown, Gniezno]
  • A. Gniezno chosen
    Gniezno is a historic city in west-central Poland, renowned as the country’s first capital and an early center of Polish statehood and Christianity.
  • B. Lidzbark Warmiński
    Lidzbark Warmiński is a historic town in northern Poland known for its well-preserved Gothic castle and role as a former seat of the Warmian bishops.
  • C. Płock
    Płock is a historic city in central Poland known for its medieval architecture and scenic location on the banks of the Vistula River.
  • D. Toruń
    Toruń is a historic city in northern Poland, renowned for its well-preserved medieval Old Town and as the birthplace of astronomer Nicolaus Copernicus.
  • E. Augustów
    Augustów is a town in northeastern Poland known for its lakes, forests, and popular water tourism, including the historic Augustów Canal.
  • 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_69b3453f759881909b91f01a1e82c036 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34ec036e8819087d8585170707545 completed March 12, 2026, 11:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69b6721dcf28819080b6a265152059e9 completed March 15, 2026, 8:47 a.m.
Created at: March 12, 2026, 11:06 p.m.