Triple
T6840868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Šešupė River |
E157568
|
entity |
| Predicate | transboundaryWatercourse |
P66357
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Šešupė River, transboundaryWatercourse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transboundaryWatercourse Context triple: [Šešupė River, transboundaryWatercourse, true]
-
A.
transboundaryWaterManagement
Indicates the cooperative planning, regulation, and use of shared water resources that cross political or administrative boundaries between different jurisdictions.
-
B.
transboundaryBasin
chosen
Indicates that a river basin or watershed extends across and is shared by the territories of two or more political or administrative jurisdictions.
-
C.
shareWaterBoundary
Indicates that two entities are adjacent to each other with a shared boundary formed by a body of water.
-
D.
watercourseIDCountry
Indicates that a specific watercourse is associated with, located in, or flows through a particular country.
-
E.
transboundaryContext
Indicates a context, situation, or effect that crosses or involves the boundaries between two or more distinct jurisdictions, regions, or territories.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b4a1f88190b4f532828697fbd8 |
completed | March 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.