Triple
T9190797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piecki |
E220583
|
entity |
| Predicate | isSeatOf |
P62
|
FINISHED |
| Object | Gmina Piecki |
E783925
|
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 Piecki | Statement: [Piecki, isSeatOf, Gmina Piecki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Piecki Context triple: [Piecki, isSeatOf, Gmina Piecki]
-
A.
Gmina Piecki
chosen
Gmina Piecki is a rural administrative district in northern Poland, known for its lakes and forests within the Warmian-Masurian Voivodeship.
-
B.
Gmina Piekoszów
Gmina Piekoszów is a rural administrative district in south-central Poland, located in the Świętokrzyskie Voivodeship.
-
C.
Gmina Pińczów
Gmina Pińczów is an administrative district (gmina) in south-central Poland that includes the town of Pińczów and surrounding rural areas.
-
D.
Gmina Pieniężno
Gmina Pieniężno is an administrative district (gmina) in northern Poland that includes the town of Pieniężno and surrounding rural areas.
-
E.
Gmina Pisz
Gmina Pisz is an urban-rural administrative district in northern Poland centered on the town of Pisz in the Warmian-Masurian 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_69ca83e7ba70819088b74866d9da2c30 |
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.