Triple

T13080781
Position Surface form Disambiguated ID Type / Status
Subject Warsaw Voivodeship E310195 entity
Predicate contains P35 FINISHED
Object Pruszków 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: Pruszków | Statement: [Warsaw Voivodeship, contains, Pruszków]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pruszków
Context triple: [Warsaw Voivodeship, contains, Pruszków]
  • A. Pruszków chosen
    Pruszków is a town in east-central Poland that functions as a suburban satellite of Warsaw within its metropolitan area.
  • B. Wołomin
    Wołomin is a town in east-central Poland that functions as a suburban community within the greater Warsaw metropolitan area.
  • C. Pułtusk
    Pułtusk is a historic town in east-central Poland, known for its medieval heritage and its role as the site of several significant battles, including during the Napoleonic Wars.
  • D. Ostrołęka
    Ostrołęka is a town in east-central Poland known for its historical role in the Napoleonic Wars and as a local industrial and administrative center.
  • E. Ciechanów
    Ciechanów is a historic town in east-central Poland, known as a regional center of the Mazovian area with a medieval castle and long-standing cultural traditions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d806a733548190989cfd4ce981ca33 completed April 9, 2026, 8:05 p.m.
NER Named-entity recognition batch_69d98119cb7081908b78ffe83ec99851 completed April 10, 2026, 11 p.m.
Created at: April 9, 2026, 9:01 p.m.