Triple
T24884163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клязьма |
E622801
|
entity |
| Predicate | входит в речную систему |
P1009
|
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.
isTributaryOfCountryLongestRiverSystem
Indicates that a river serves as a tributary within the longest river system of a specified country.
-
B.
tributarySystem
Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
-
C.
riverSystem
chosen
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
D.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
-
E.
тип реки
Indicates the classification or category of a river based on its characteristics or role.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:25 a.m.