Triple

T2419030
Position Surface form Disambiguated ID Type / Status
Subject Edward Gierek E52373 entity
Predicate residence P75 FINISHED
Object Sosnowiec E426926 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: Sosnowiec | Statement: [Edward Gierek, residence, Sosnowiec]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sosnowiec
Context triple: [Edward Gierek, residence, Sosnowiec]
  • A. Sosnowiec chosen
    Sosnowiec is an industrial city in southern Poland, located in the Silesian Voivodeship and known as part of the Upper Silesian metropolitan area.
  • B. Chorzów
    Chorzów is an industrial city in southern Poland’s Silesian region, known for its heavy industry heritage and the extensive Silesian Park.
  • C. Polkowice
    Polkowice is a town in southwestern Poland known for its copper mining industry and location within the Lower Silesian region.
  • D. Kociewie
    Kociewie is an ethnocultural region in northern Poland known for its distinct folk traditions, dialect, and rural landscapes.
  • E. Glogów
    Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
  • 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_69ab495622948190bc6bc6e4cddaf645 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abc96e1b3881909de57501b5d4099a completed March 7, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69b5c6c93644819096e65532945f9763 completed March 14, 2026, 8:36 p.m.
Created at: March 6, 2026, 9:42 p.m.