Triple

T9190004
Position Surface form Disambiguated ID Type / Status
Subject Wielbark E220557 entity
Predicate partOf P40 FINISHED
Object Gmina Wielbark E788132 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 Wielbark | Statement: [Wielbark, partOf, Gmina Wielbark]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Wielbark
Context triple: [Wielbark, partOf, Gmina Wielbark]
  • A. Gmina Wielbark chosen
    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.
  • B. Gmina Zalewo
    Gmina Zalewo is an administrative district (gmina) in northern Poland that includes the town of Zalewo and surrounding rural areas.
  • 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 Zawichost
    Gmina Zawichost is a rural administrative district in south-eastern Poland, centered on the historic town of Zawichost in the Świętokrzyskie Voivodeship.
  • E. Gmina Bielawy
    Gmina Bielawy is a rural administrative district in central Poland, known for encompassing several villages and agricultural areas.
  • 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_69ca83e6d77c81909862b7afef56b1bf completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd5bd8c5c81909d0cdbcd7410fcee completed April 1, 2026, 8:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0b1adc2508190b8a24510ee61f092 completed April 4, 2026, 6:37 a.m.
Created at: March 30, 2026, 7:24 p.m.