Triple
T6115419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pińczów County |
E136347
|
entity |
| Predicate | containsGminaType |
P10835
|
FINISHED |
| Object | urban-rural gmina |
—
|
LITERAL 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: urban-rural gmina | Statement: [Pińczów County, containsGminaType, urban-rural gmina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsGminaType Context triple: [Pińczów County, containsGminaType, urban-rural gmina]
-
A.
hasGmina
Indicates that an entity is administratively associated with, or belongs to, a specific gmina (a basic local government unit/municipality).
-
B.
hasMunicipalityType
chosen
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
C.
hasRuralGmina
Indicates that an entity (typically an administrative unit) includes or is associated with a specific rural gmina as part of its jurisdiction or structure.
-
D.
hasUrbanGmina
Indicates that an entity is associated with, or contains, an urban gmina (a type of urban municipality or commune).
-
E.
hasUrbanGminaStatus
Indicates that an administrative unit holds the legal status of an urban gmina (urban municipality).
- F. None of above.
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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bc246e48190b4f3d52eb682aa45 |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.