Triple
T9190662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rozogi |
E220579
|
entity |
| Predicate | gminaType |
P86731
|
FINISHED |
| Object | 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: rural gmina | Statement: [Rozogi, gminaType, rural gmina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gminaType Context triple: [Rozogi, gminaType, 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.
hasGminaStatus
Indicates that an administrative unit holds the official legal status of a gmina (municipality/commune) within a country’s territorial division.
-
C.
hasUrbanRuralGmina
Indicates that an entity is associated with a specific urban-rural gmina (a mixed urban and rural municipal administrative unit).
-
D.
hasUrbanGmina
Indicates that an entity is associated with, or contains, an urban gmina (a type of urban municipality or commune).
-
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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5bf25c081909e651b67ef8ecc33 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:24 p.m.