Triple
T31297192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Zabłudów |
E798110
|
entity |
| Predicate | administrativeCategory |
P29075
|
FINISHED |
| Object | rural municipality |
—
|
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 municipality | Statement: [Gmina Zabłudów, administrativeCategory, rural municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeCategory Context triple: [Gmina Zabłudów, administrativeCategory, rural municipality]
-
A.
governedCategory
Indicates that one category is subject to the control, regulation, or authority of another entity or governing framework.
-
B.
canonicalCategory
chosen
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
C.
administrativelyIn
Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
-
D.
administrativeFeature
Indicates that one entity serves as an administrative or governance-related feature, function, or attribute associated with another entity.
-
E.
functionCategory
Indicates that one function is classified as belonging to a particular functional category or type.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 9:14 p.m.