Triple

T14569568
Position Surface form Disambiguated ID Type / Status
Subject Wolbrom E341873 entity
Predicate gmina P852 FINISHED
Object Gmina Wolbrom E341876 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: Gmina Wolbrom | Statement: [Wolbrom, gmina, Gmina Wolbrom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Wolbrom
Context triple: [Wolbrom, gmina, Gmina Wolbrom]
  • A. Gmina Wolbrom chosen
    Gmina Wolbrom is an administrative district and town-centered municipality in southern Poland’s Lesser Poland Voivodeship.
  • B. Gmina Wielbark
    Gmina Wielbark is a rural administrative district in northern Poland’s Warmian-Masurian Voivodeship, centered on the village of Wielbark and encompassing surrounding villages and countryside.
  • C. Gmina Włoszczowa
    Gmina Włoszczowa is an administrative district in south-central Poland that includes the town of Włoszczowa and surrounding rural areas.
  • D. Gmina Wolin
    Gmina Wolin is an urban-rural administrative district in north-western Poland centered on the historic town of Wolin.
  • E. Gmina Gubin
    Gmina Gubin is a rural administrative district in western Poland, situated in Lubusz Voivodeship near the German border.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f2121481908f2385637944785d completed April 14, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8ac858108190b7c90130f18b0ddb completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:23 a.m.