Triple

T26917074
Position Surface form Disambiguated ID Type / Status
Subject Bobrowniki E677544 entity
Predicate locatedInIndustrialRegion P49790 FINISHED
Object Upper Silesia NE NERFINISHED

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: Upper Silesia | Statement: [Bobrowniki, locatedInIndustrialRegion, Upper Silesia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInIndustrialRegion
Context triple: [Bobrowniki, locatedInIndustrialRegion, Upper Silesia]
  • A. locatedInIndustrialCity
    Indicates that something is situated within a city characterized primarily by industrial activity and facilities.
  • B. partOfIndustrialRegion chosen
    Indicates that an entity is located within or belongs to a broader industrial region or industrially developed area.
  • C. isIndustrialRegion
    Indicates that a given area functions primarily as a center of industrial activity, characterized by significant manufacturing, production, or related industrial operations.
  • D. locatedInFormerIndustrialArea
    Indicates that an entity is situated within an area that was previously used for industrial purposes but is no longer active as such.
  • E. connectsToIndustrialArea
    Indicates that one entity has a direct link, route, or access connection to an industrial area.
  • F. None of above.

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_69eee9bdebc48190ba90a12a63e09c73 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69fe38be079c8190a240191ac0e73e3a completed May 8, 2026, 7:25 p.m.
PD Predicate disambiguation batch_69fe350344508190930de2218156ca02 completed May 8, 2026, 7:09 p.m.
Created at: April 27, 2026, 6:05 a.m.