Triple
T24884159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клязьма |
E622801
|
entity |
| Predicate | является притоком |
P415
|
FINISHED |
| Object | Ока |
—
|
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: Ока | Statement: [Клязьма, является притоком, Ока]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: является притоком Context triple: [Клязьма, является притоком, Ока]
-
A.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
B.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
C.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
D.
tributary
chosen
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
E.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
- 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.