Triple
T30523720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NUTS region PL82 (Podkarpackie) |
E776771
|
entity |
| Predicate | bordersPolishRegion |
P192043
|
FINISHED |
| Object | Lublin Voivodeship |
—
|
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: Lublin Voivodeship | Statement: [NUTS region PL82 (Podkarpackie), bordersPolishRegion, Lublin Voivodeship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bordersPolishRegion Context triple: [NUTS region PL82 (Podkarpackie), bordersPolishRegion, Lublin Voivodeship]
-
A.
sharesBorderWithPolishVoivodeship
chosen
Indicates that one entity has a land or water boundary directly adjoining a Polish voivodeship.
-
B.
borderingBelarusRegion
Indicates that one region shares a land border with a region located in Belarus.
-
C.
bordersSubregion
Indicates that one region shares a boundary with a smaller, contained subregion.
-
D.
bordersVia
Indicates that two entities share a boundary or border that is specifically established, defined, or mediated through a particular intermediate feature, route, or medium.
-
E.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: April 29, 2026, 8:17 p.m.