Triple
T24856560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libiąż |
E622044
|
entity |
| Predicate | isUrbanGminaSeat |
P154274
|
FINISHED |
| Object | Gmina Libiąż |
—
|
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 Libiąż | Statement: [Libiąż, isUrbanGminaSeat, Gmina Libiąż]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanGminaSeat Context triple: [Libiąż, isUrbanGminaSeat, Gmina Libiąż]
-
A.
isUrbanGminaOf
chosen
Indicates that one entity is an urban gmina (a municipality with city status) that administratively belongs to or governs the other entity.
-
B.
hasUrbanGmina
Indicates that an entity is associated with, or contains, an urban gmina (a type of urban municipality or commune).
-
C.
hasUrbanGminaStatus
Indicates that an administrative unit holds the legal status of an urban gmina (urban municipality).
-
D.
regionalCapitalOfVoivodeship
Indicates that a location serves as the administrative capital of a specific voivodeship (province or region).
-
E.
isRuralUrbanGmina
Indicates that a given administrative district (gmina) is classified as a mixed rural-urban municipality, combining both town and countryside areas.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.