Triple
T9190388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budry |
E220570
|
entity |
| Predicate | isSeatOf |
P62
|
FINISHED |
| Object | Gmina Budry |
E783905
|
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 Budry | Statement: [Budry, isSeatOf, Gmina Budry]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Budry Context triple: [Budry, isSeatOf, Gmina Budry]
-
A.
Gmina Budry
chosen
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.
-
B.
Gmina Budzów
Gmina Budzów is a rural administrative district in southern Poland, located in Lesser Poland Voivodeship.
-
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 Bielawy
Gmina Bielawy is a rural administrative district in central Poland, known for encompassing several villages and agricultural areas.
-
E.
Gmina Susz
Gmina Susz is an administrative district (gmina) in northern Poland that includes the town of Susz and 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_69ccd5bf25c081909e651b67ef8ecc33 |
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.