Triple
T21182648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Masłów |
E521990
|
entity |
| Predicate | neighbouringAdministrativeUnit |
P33892
|
FINISHED |
| Object | Kielce |
—
|
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: Kielce | Statement: [Gmina Masłów, neighbouringAdministrativeUnit, Kielce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighbouringAdministrativeUnit Context triple: [Gmina Masłów, neighbouringAdministrativeUnit, Kielce]
-
A.
neighbouringMunicipality
chosen
Indicates that one municipality directly borders and is adjacent to another municipality.
-
B.
hasNeighboringLGA
Indicates that one local government area is geographically adjacent to or directly borders another local government area.
-
C.
neighboringRegion
Indicates that two regions share a common boundary or are directly adjacent to each other geographically.
-
D.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
E.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301eb3248190b9f6fc1586651fec |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:04 p.m.