Triple
T12740508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciechanów County |
E304475
|
entity |
| Predicate | containsRuralGmina |
P46876
|
FINISHED |
| Object | Gmina Sońsk |
E1001205
|
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 Sońsk | Statement: [Ciechanów County, containsRuralGmina, Gmina Sońsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Sońsk Context triple: [Ciechanów County, containsRuralGmina, Gmina Sońsk]
-
A.
Gmina Sońsk
chosen
Gmina Sońsk is a rural administrative district in east-central Poland, located within the Masovian Voivodeship.
-
B.
Gmina Sokółka
Gmina Sokółka is an administrative district (gmina) in northeastern Poland that includes the town of Sokółka and surrounding rural areas.
-
C.
Gmina Końskie
Gmina Końskie is an administrative district in south-central Poland that includes the town of Końskie and surrounding rural areas within Końskie County.
-
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 Gnojno
Gmina Gnojno is a rural administrative district in south-central Poland, located within the Świętokrzyskie 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96facb2d48190bc12efc00c9da360 |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684eba2508190966d084cc21dc1ea |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:26 p.m.