Triple
T34885217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jelenia Góra Voivodeship (former) |
E1006124
|
entity |
| Predicate | hadBorderFunction |
P97842
|
FINISHED |
| Object | border voivodeship of Poland |
—
|
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: border voivodeship of Poland | Statement: [Jelenia Góra Voivodeship (former), hadBorderFunction, border voivodeship of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBorderFunction Context triple: [Jelenia Góra Voivodeship (former), hadBorderFunction, border voivodeship of Poland]
-
A.
hadBorder
Indicates that one entity shared a common boundary or frontier with another entity during a specified time period.
-
B.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
C.
hasBorderFunctionWith
chosen
Indicates a relationship where one entity serves a boundary-related role or function in conjunction with another entity.
-
D.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
E.
hasBordersBy
Indicates that one entity shares a boundary or border with another entity.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.