Triple

T6613136
Position Surface form Disambiguated ID Type / Status
Subject Silesian Voivodeship E149284 entity
Predicate containsCity P294 FINISHED
Object Chorzów E241511 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: Chorzów | Statement: [Silesian Voivodeship, containsCity, Chorzów]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chorzów
Context triple: [Silesian Voivodeship, containsCity, Chorzów]
  • A. Chorzów chosen
    Chorzów is an industrial city in southern Poland’s Silesian region, known for its heavy industry heritage and the extensive Silesian Park.
  • B. Gliwice
    Gliwice is a historic industrial and academic city in southern Poland’s Silesian region, known for its engineering university and the landmark Gliwice Radio Tower.
  • C. Stalowa Wola
    Stalowa Wola is an industrial city in southeastern Poland, historically known as a major center of heavy industry and steel production.
  • D. Sosnowiec
    Sosnowiec is an industrial city in southern Poland, located in the Silesian Voivodeship and known as part of the Upper Silesian metropolitan area.
  • E. Tychy
    Tychy is a city in the Silesian region of southern Poland, known for its brewing industry and role as a planned industrial 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_69c687ebc680819094caf71faba2efe2 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6af3890408190a0edf2f813b93196 completed March 27, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69cfb9e1afb08190a1befb047ee96ca8 completed April 3, 2026, 1 p.m.
Created at: March 27, 2026, 1:57 p.m.