Triple

T20745017
Position Surface form Disambiguated ID Type / Status
Subject Kielce Voivodeship (1945–1998) E510556 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Przysucha 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: Przysucha | Statement: [Kielce Voivodeship (1945–1998), containsAdministrativeTerritorialEntity, Przysucha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Przysucha
Context triple: [Kielce Voivodeship (1945–1998), containsAdministrativeTerritorialEntity, Przysucha]
  • A. Przysucha chosen
    Przysucha is a small town in central Poland known for its historical ties to Jewish culture and its location within the Masovian region.
  • B. Sułów
    Sułów is a village in eastern Poland located within Zamość County in the Lublin Voivodeship.
  • C. Pyrzyce
    Pyrzyce is a historic town in northwestern Poland known for its medieval fortifications and location within the West Pomeranian region.
  • D. Pszczyna
    Pszczyna is a historic town in southern Poland known for its well-preserved castle complex and picturesque old town.
  • E. Wiślica
    Wiślica is a historic town in south-central Poland, known for its medieval architecture and archaeological significance as one of the country’s oldest settlements.
  • 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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c212b744819089bc1d47a020bd61 completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:33 p.m.