Triple
T21914519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Sandomierz |
E541149
|
entity |
| Predicate | officialName |
P66
|
FINISHED |
| Object | Gmina Sandomierz |
—
|
NE NERFINISHED |
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 Sandomierz | Statement: [Gmina Sandomierz, officialName, Gmina Sandomierz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Sandomierz Context triple: [Gmina Sandomierz, officialName, Gmina Sandomierz]
-
A.
Gmina Sandomierz
chosen
Gmina Sandomierz is an administrative district in south-eastern Poland centered around the historic town of Sandomierz in the Świętokrzyskie Voivodeship.
-
B.
Gmina Sieradz
Gmina Sieradz is a rural administrative district in central Poland, surrounding the town of Sieradz in the Łódź Voivodeship.
-
C.
Gmina Samborzec
Gmina Samborzec is a rural administrative district in southeastern Poland, located in the Świętokrzyskie 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 Mielec
Gmina Mielec is an administrative district (gmina) in southeastern Poland, located in the Subcarpathian Voivodeship and centered around the town of Mielec.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123366cb88190a42aa741e1245fd9 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 16, 2026, 7:42 p.m.