Triple
T34845223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bug River near Włodawa |
E1004445
|
entity |
| Predicate | administrativeBorderOf |
P47901
|
FINISHED |
| Object | Lublin Voivodeship border section |
—
|
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 border section | Statement: [Bug River near Włodawa, administrativeBorderOf, Lublin Voivodeship border section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeBorderOf Context triple: [Bug River near Włodawa, administrativeBorderOf, Lublin Voivodeship border section]
-
A.
borderingAdministrativeTerritorialEntity
Indicates that one administrative territorial entity shares a common boundary with another administrative territorial entity.
-
B.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
C.
countyBorder
Indicates that two counties 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.
isPoliticalBoundary
chosen
Indicates that one entity serves as a dividing line or border that separates distinct political or administrative jurisdictions.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4 p.m.