Triple
T24386041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Przeciszów |
E614751
|
entity |
| Predicate | borderedByAdministrativeEntity |
P120977
|
FINISHED |
| Object | Gmina Oświęcim |
—
|
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 Oświęcim | Statement: [Gmina Przeciszów, borderedByAdministrativeEntity, Gmina Oświęcim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByAdministrativeEntity Context triple: [Gmina Przeciszów, borderedByAdministrativeEntity, Gmina Oświęcim]
-
A.
borderingAdministrativeTerritorialEntity
chosen
Indicates that one administrative territorial entity shares a common boundary with another administrative territorial entity.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
D.
borderingAuthorityOf
Indicates that one authority’s jurisdiction directly touches or shares a boundary with another authority’s jurisdiction.
-
E.
countyBorder
Indicates that two counties share a common boundary or border with each other.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29454c36c8190b7820dbf5af7b695 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.