Triple
T11627250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Прут |
E276302
|
entity |
| Predicate | типПограничнойРеки |
P93095
|
FINISHED |
| Object | межгосударственная граница |
—
|
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: межгосударственная граница | Statement: [Прут, типПограничнойРеки, межгосударственная граница]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: типПограничнойРеки Context triple: [Прут, типПограничнойРеки, межгосударственная граница]
-
A.
transboundaryRiverOf
chosen
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
B.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
C.
borderingUnitType
Indicates that one unit is adjacent to another unit of a specified type along a shared boundary.
-
D.
transboundaryBasin
Indicates that a river basin or watershed extends across and is shared by the territories of two or more political or administrative jurisdictions.
-
E.
borderRiverContext
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1259cd08190a75eeacb5e39b858 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.