Triple

T17295989
Position Surface form Disambiguated ID Type / Status
Subject Targówek E419910 entity
Predicate hasSubdivision P747 FINISHED
Object Targówek Fabryczny E419910 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: Targówek Fabryczny | Statement: [Targówek, hasSubdivision, Targówek Fabryczny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Targówek Fabryczny
Context triple: [Targówek, hasSubdivision, Targówek Fabryczny]
  • A. Targówek chosen
    Targówek is a residential district in the northeastern part of Warsaw, Poland, known for its large housing estates, green areas, and growing transport links to the city center.
  • B. Stalowa Wola
    Stalowa Wola is an industrial city in southeastern Poland, historically known as a major center of heavy industry and steel production.
  • C. Tychy
    Tychy is a city in the Silesian region of southern Poland, known for its brewing industry and role as a planned industrial center.
  • D. Jaworzno
    Jaworzno is a city in southern Poland, located in the Silesian Voivodeship and known for its industrial heritage and role in the Upper Silesian urban area.
  • E. Łódź Fabryczna
    Łódź Fabryczna is a major modern railway terminus in Łódź, Poland, serving as one of the city’s primary long-distance and regional train hubs.
  • 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_69d886db32608190a61e18862c5a8af6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e437875b208190bcf0df2ded546257 completed April 19, 2026, 2:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180d881ec81908e794143d355effe completed May 11, 2026, 7:10 a.m.
Created at: April 10, 2026, 5:40 a.m.