Triple

T2715593
Position Surface form Disambiguated ID Type / Status
Subject Koło E59958 entity
Predicate locatedEastOf P4240 FINISHED
Object Poznań E14540 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: Poznań | Statement: [Koło, locatedEastOf, Poznań]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poznań
Context triple: [Koło, locatedEastOf, Poznań]
  • A. Poznań chosen
    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.
  • B. Wrocław
    Wrocław is a major historic city in southwestern Poland, known for its picturesque Old Town, numerous bridges over the Oder River, and role as a cultural and academic center.
  • 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. Opole
    Opole is a historic city in southwestern Poland, known as one of the country’s oldest urban centers and a regional cultural hub.
  • E. Kraków
    Kraków is one of Poland’s oldest and most historically significant cities, renowned for its well-preserved medieval core, royal heritage, and cultural institutions.
  • 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_69ab4ac92a088190bc74bca14038e3de completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abda94d3288190bd60bc886e2106c7 completed March 7, 2026, 7:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69b555ff48c48190865f0d588ec5d296 completed March 14, 2026, 12:35 p.m.
Created at: March 6, 2026, 9:55 p.m.