Triple

T706438
Position Surface form Disambiguated ID Type / Status
Subject Leiden E14108 entity
Predicate twinCity P1072 FINISHED
Object Torun E44061 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: Torun | Statement: [Leiden, twinCity, Torun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Torun
Context triple: [Leiden, twinCity, Torun]
  • A. Toruń chosen
    Toruń is a historic city in northern Poland, renowned for its well-preserved medieval Old Town and as the birthplace of astronomer Nicolaus Copernicus.
  • B. Opole
    Opole is a historic city in southwestern Poland, known as one of the country’s oldest urban centers and a regional cultural hub.
  • C. Poznań
    Poznań is a historic and economically significant city in western Poland, known for its medieval Old Town, role as an early center of Polish statehood, and status as a major academic and industrial hub.
  • D. Gdańsk
    Gdańsk is a major Polish port city on the Baltic Sea, known for its rich Hanseatic history, shipyards, and role in the origins of the Solidarity movement.
  • E. Szczecin
    Szczecin is a large Polish city and important maritime and industrial center in northwestern Poland, situated near the Baltic Sea and the German border.
  • 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_69a493494ec48190ae6751683625a9ba completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a54607f08190b3ee4805f2ea4b2f completed March 1, 2026, 8:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7c005750881909187edfa8e8fa02c completed March 4, 2026, 5:15 a.m.
Created at: March 1, 2026, 7:36 p.m.