Triple
T15031900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorohusk |
E378373
|
entity |
| Predicate | isSeatOf |
P62
|
FINISHED |
| Object | Gmina Dorohusk |
E1134431
|
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 Dorohusk | Statement: [Dorohusk, isSeatOf, Gmina Dorohusk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Dorohusk Context triple: [Dorohusk, isSeatOf, Gmina Dorohusk]
-
A.
Gmina Dorohusk
chosen
Gmina Dorohusk is a rural administrative district in eastern Poland, situated near the border with Ukraine in Chełm County, Lublin Voivodeship.
-
B.
Gmina Gorlice
Gmina Gorlice is an administrative district in southern Poland that encompasses the town of Gorlice and surrounding rural areas.
-
C.
Gmina Puńsk
Gmina Puńsk is a rural administrative district in northeastern Poland, near the Lithuanian border, known for its significant Lithuanian minority and bilingual cultural character.
-
D.
Gmina Grudusk
Gmina Grudusk is a rural administrative district in east-central Poland, situated in Ciechanów County within the Masovian Voivodeship.
-
E.
Gmina Morąg
Gmina Morąg is an urban-rural administrative district in northern Poland’s Warmian-Masurian Voivodeship, centered on the town of Morąg.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7e2416081908dfba48d7f7b4a84 |
completed | April 15, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5b4d58481908afbc89263e07b50 |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 10, 2026, 2:59 a.m.