Triple

T15967785
Position Surface form Disambiguated ID Type / Status
Subject Supreme Administrative Court of Poland E387238 entity
Predicate hasBranch P35 FINISHED
Object Gdańsk E18213 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: Gdańsk | Statement: [Supreme Administrative Court of Poland, hasBranch, Gdańsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gdańsk
Context triple: [Supreme Administrative Court of Poland, hasBranch, Gdańsk]
  • A. Gdańsk chosen
    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.
  • B. Gdynia
    Gdynia is a major seaport city on Poland’s Baltic coast, developed rapidly in the 20th century into one of the country’s key maritime and economic centers.
  • C. Bydgoszcz
    Bydgoszcz is a major city in northern Poland known as an important economic, cultural, and academic center on the Brda and Vistula rivers.
  • D. 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.
  • E. Koszalin
    Koszalin is a city in northwestern Poland near the Baltic Sea, known as a regional cultural and economic center.
  • 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_69d86da94ccc819083d187f5dc6a123e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e157277e7881908d49f4874766b3b5 completed April 16, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a005804f5c08190b545bc8b65e953f7 completed May 10, 2026, 10:03 a.m.
Created at: April 10, 2026, 4:54 a.m.