Triple

T1184666
Position Surface form Disambiguated ID Type / Status
Subject Gorlice E25217 entity
Predicate isSeatOf P62 FINISHED
Object Gorlice County E171668 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: Gorlice County | Statement: [Gorlice, isSeatOf, Gorlice County]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gorlice County
Context triple: [Gorlice, isSeatOf, Gorlice County]
  • A. Gorlice County chosen
    Gorlice County is a local government and administrative district in southern Poland’s Lesser Poland Voivodeship, known for its historic towns and proximity to the Carpathian foothills.
  • B. Pińczów County
    Pińczów County is an administrative district in south-central Poland, known for its rural landscapes, historic towns, and location within the Świętokrzyskie region.
  • C. Włoszczowa County
    Włoszczowa County is an administrative district in south-central Poland, with its seat in the town of Włoszczowa.
  • D. Tatra County
    Tatra County is an administrative region in southern Poland, known for encompassing the Tatra Mountains and the popular resort town of Zakopane.
  • E. Kielce County
    Kielce County is an administrative district in south-central Poland, centered around the city of Kielce within the Świętokrzyskie region.
  • 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_69a49427d98881908646d6c63b8cea1e completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd39245881908766c41943dc2752 completed March 1, 2026, 10:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad293648d08190a1c15fe677aa7b8c completed March 8, 2026, 7:45 a.m.
Created at: March 1, 2026, 7:45 p.m.