Triple

T5888336
Position Surface form Disambiguated ID Type / Status
Subject Gmina Skawina E130924 entity
Predicate seat P75 FINISHED
Object Skawina E23073 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: Skawina | Statement: [Gmina Skawina, seat, Skawina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skawina
Context triple: [Gmina Skawina, seat, Skawina]
  • A. Skawina chosen
    Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
  • B. Mława
    Mława is a town in north-central Poland known for its historical significance, including a major World War II battle, and its regional cultural and economic role.
  • C. Słupia
    Słupia is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
  • D. Muszyna
    Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
  • E. Głuszyna
    Głuszyna is a locality in present-day Poland known as the birthplace of the 19th-century Polish explorer and geologist Paweł Edmund Strzelecki.
  • 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_69c0085628dc8190b334c1b44c067efc completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c036af6330819081d9fa98a8c26633 completed March 22, 2026, 6:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c124f946348190ab6fa7c2c203924f completed March 23, 2026, 11:33 a.m.
Created at: March 22, 2026, 3:58 p.m.