Triple
T9190190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purda |
E220562
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Gmina Purda |
E783897
|
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 Purda | Statement: [Purda, partOf, Gmina Purda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Purda Context triple: [Purda, partOf, Gmina Purda]
-
A.
Gmina Purda
chosen
Gmina Purda is a rural administrative district in northern Poland known for its forests, lakes, and villages near the city of Olsztyn.
-
B.
Gmina Budry
Gmina Budry is a rural administrative district in northern Poland, known for its small villages and proximity to the border with Russia’s Kaliningrad Oblast.
-
C.
Gmina Grudusk
Gmina Grudusk is a rural administrative district in east-central Poland, situated in Ciechanów County within the Masovian Voivodeship.
-
D.
Gmina Susz
Gmina Susz is an administrative district (gmina) in northern Poland that includes the town of Susz and surrounding rural areas.
-
E.
Gmina Prabuty
Gmina Prabuty is an administrative district (gmina) in northern Poland that encompasses the town of Prabuty and its surrounding rural 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_69d077797be081908300a5baa0041ce5 |
completed | April 4, 2026, 2:29 a.m. |
Created at: March 30, 2026, 7:24 p.m.