Triple
T19281855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poronin |
E482207
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Gmina Poronin |
—
|
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 Poronin | Statement: [Poronin, partOf, Gmina Poronin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Poronin Context triple: [Poronin, partOf, Gmina Poronin]
-
A.
Gmina Poronin
chosen
Gmina Poronin is a rural administrative district in southern Poland, located in the Tatra Mountains region near the resort town of Zakopane.
-
B.
Gmina Gnojno
Gmina Gnojno is a rural administrative district in south-central Poland, located within the Świętokrzyskie Voivodeship.
-
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 Susz
Gmina Susz is an administrative district (gmina) in northern Poland that includes the town of Susz and surrounding rural areas.
-
E.
Gmina Kampinos
Gmina Kampinos is a rural administrative district in east-central Poland, located in the Masovian Voivodeship and known for encompassing part of the Kampinos National Park.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbff1e6c819094ae6a5ad40adb65 |
completed | April 20, 2026, 10:12 a.m. |
Created at: April 10, 2026, 1:30 p.m.