Triple
T23873502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zawiercie |
E592792
|
entity |
| Predicate | isUrbanGminaOf |
P154274
|
FINISHED |
| Object | Zawiercie County |
—
|
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: Zawiercie County | Statement: [Zawiercie, isUrbanGminaOf, Zawiercie County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanGminaOf Context triple: [Zawiercie, isUrbanGminaOf, Zawiercie County]
-
A.
hasUrbanGmina
Indicates that an entity is associated with, or contains, an urban gmina (a type of urban municipality or commune).
-
B.
hasUrbanGminaStatus
Indicates that an administrative unit holds the legal status of an urban gmina (urban municipality).
-
C.
isRuralUrbanGmina
Indicates that a given administrative district (gmina) is classified as a mixed rural-urban municipality, combining both town and countryside areas.
-
D.
hasUrbanRuralGmina
Indicates that an entity is associated with a specific urban-rural gmina (a mixed urban and rural municipal administrative unit).
-
E.
hasUrbanRuralGminas
Indicates that an administrative unit (such as a county or region) includes one or more gminas that are classified as mixed urban-rural municipalities.
- F. None of above. chosen
Provenance (4 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbff91788190b7aabe285014b873 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:14 p.m.