Triple
T30011151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inowrocław County |
E762462
|
entity |
| Predicate | administrativeSeatType |
P5164
|
FINISHED |
| Object | urban 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 gmina | Statement: [Inowrocław County, administrativeSeatType, urban gmina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeSeatType Context triple: [Inowrocław County, administrativeSeatType, urban gmina]
-
A.
administrativeHeadquarter
Indicates the location that serves as the main administrative center or headquarters for an organization or governing body.
-
B.
administrativeOffice
Indicates that one entity serves as the administrative office or central administrative unit responsible for managing or overseeing the affairs of another entity.
-
C.
headquartersOfOffice
Indicates that a particular location serves as the main headquarters for a specified office or organizational unit.
-
D.
hasOfficeType
chosen
Indicates that an entity’s office is classified as a specific type or category of office.
-
E.
locationOfGoverningBody
Indicates the place where a governing body is based or carries out its official functions.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 6:44 p.m.