Triple
T24884160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клязьма |
E622801
|
entity |
| Predicate | тип притока |
P150479
|
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.
тип реки
Indicates the classification or category of a river based on its characteristics or role.
-
B.
flowType
Indicates the kind or category of flow (such as direction, pattern, or mode of movement/transfer) that characterizes the relationship between entities.
-
C.
inflowTo
Indicates that something (such as a fluid, resource, or quantity) flows or moves into a specified target or destination.
-
D.
inletType
chosen
Indicates the specific kind or category of inlet through which something (such as a fluid, signal, or material) enters a system or component.
-
E.
primaryConduitType
Indicates the main type or category of conduit used as the primary pathway for a connection or flow between entities.
- 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.