Triple
T37031098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus–Poland waterway network |
E916496
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transboundary infrastructure |
C9303
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: transboundary infrastructure Context triple: [Belarus–Poland waterway network, instanceOf, transboundary infrastructure]
-
A.
cross-border energy infrastructure project
A cross-border energy infrastructure project is a coordinated initiative to plan, finance, build, and operate energy facilities—such as pipelines, transmission lines, or interconnectors—that physically link and serve multiple countries’ energy systems.
-
B.
transboundary region
A transboundary region is a geographically contiguous area that spans across the borders of two or more political or administrative jurisdictions, sharing interconnected environmental, economic, social, or cultural systems.
-
C.
cross-border transport link
chosen
A cross-border transport link is an infrastructure connection—such as a road, railway, bridge, tunnel, or ferry route—that enables the movement of people and goods between two or more countries.
-
D.
international border
An international border is a legally defined geographic boundary that separates the territories and jurisdictions of two or more sovereign states.
-
E.
transboundary river system
A transboundary river system is a network of rivers and related water bodies that cross or form political borders between two or more countries, requiring shared management and governance.
- F. None of above.
Provenance (1 batch)
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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.