Triple
T9190132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dywity |
E220560
|
entity |
| Predicate | administrativeDivision |
P747
|
FINISHED |
| Object | Gmina Dywity |
E783894
|
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 Dywity | Statement: [Dywity, administrativeDivision, Gmina Dywity]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Dywity Context triple: [Dywity, administrativeDivision, Gmina Dywity]
-
A.
Gmina Dywity
chosen
Gmina Dywity is a rural administrative district in northern Poland, located in Warmian-Masurian Voivodeship near the city of Olsztyn.
-
B.
Gmina Małdyty
Gmina Małdyty is a rural administrative district in northern Poland, located in the Warmian-Masurian Voivodeship.
-
C.
Gmina Rytro
Gmina Rytro is a rural administrative district in southern Poland, situated in the Lesser Poland Voivodeship and known for its mountainous landscapes in the Beskid Sądecki range.
-
D.
Gmina Bielawy
Gmina Bielawy is a rural administrative district in central Poland, known for encompassing several villages and agricultural areas.
-
E.
Gmina Kęty
Gmina Kęty is an urban-rural administrative district in southern Poland, centered on the town of Kęty in the Lesser Poland Voivodeship.
- 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_69d065d5e81c8190b6687999a87fd559 |
completed | April 4, 2026, 1:13 a.m. |
Created at: March 30, 2026, 7:24 p.m.