Triple

T13347278
Position Surface form Disambiguated ID Type / Status
Subject Gmina Bystra-Sidzina E317984 entity
Predicate administrativeCenter P1474 FINISHED
Object Bystra E889326 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: Bystra | Statement: [Gmina Bystra-Sidzina, administrativeCenter, Bystra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bystra
Context triple: [Gmina Bystra-Sidzina, administrativeCenter, Bystra]
  • A. Bystra
    Bystra is a prominent peak in the Western Tatras, known as the highest summit on the Slovak side of this mountain range.
  • B. Muszyna
    Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
  • C. Bystra Śląska chosen
    Bystra Śląska is a village in southern Poland, located in the Silesian Beskids near Bielsko-Biała.
  • D. Góra
    Góra is a town in southwestern Poland known as the seat of Góra County in the Lower Silesian Voivodeship.
  • E. Górowo Hills
    Górowo Hills is a hilly geographical region in northern Poland known for its rolling landscapes surrounding the town of Górowo Iławeckie.
  • 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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99e89c65c819093f3bea11d6073c5 completed April 11, 2026, 1:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69f71f439b3c8190b35fd4d097d65068 completed May 3, 2026, 10:11 a.m.
Created at: April 9, 2026, 9:31 p.m.