Triple
T17265753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Обь |
E419121
|
entity |
| Predicate | направлениеТечения |
P113696
|
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.
waterwayDirection
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
B.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
C.
flowsNorthwardsTo
Indicates that something moves or is directed in a generally northward direction until it reaches or connects with another specified entity.
-
D.
flowsNorthward
Indicates that the subject moves or travels in a generally northward direction relative to a reference frame or location.
-
E.
hasDirectionOfFlow
chosen
Indicates that something moves or is transmitted from one entity or location toward another along a specific path or orientation.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f44ec7c81909a925fc8692b0a6c |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.