Triple
T24289186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Trzciana |
E605763
|
entity |
| Predicate | neighboringAdministrativeEntity |
P33892
|
FINISHED |
| Object | Gmina Żegocina |
—
|
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 Żegocina | Statement: [Gmina Trzciana, neighboringAdministrativeEntity, Gmina Żegocina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringAdministrativeEntity Context triple: [Gmina Trzciana, neighboringAdministrativeEntity, Gmina Żegocina]
-
A.
neighbouringMunicipality
chosen
Indicates that one municipality directly borders and is adjacent to another municipality.
-
B.
administrativeTerritorialEntityOf
Indicates that one entity serves as the administrative territorial unit or jurisdiction to which another entity belongs or is governed by.
-
C.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
D.
nearbyPoliticalEntity
Indicates that one political entity is geographically close to another political entity, without necessarily sharing a border.
-
E.
neighboringRegion
Indicates that two regions share a common boundary or are directly adjacent 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5908e08190a9f150df924a7160 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.