Triple
T32663544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Амгунь |
E835092
|
entity |
| Predicate | направлениеТеченияВНижнемТечении |
P75396
|
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
chosen
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
B.
navigableInLowerCourse
Indicates that a watercourse is suitable for navigation specifically in its lower (downstream) section.
-
C.
watercourseBelow
Indicates that one watercourse lies downstream or at a lower elevation relative to another watercourse.
-
D.
flowsDownSideOf
Indicates that one entity moves or runs downward along the side or surface of another entity.
-
E.
hasRiverBelow
Indicates that one entity is located above another such that a river lies physically below 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:08 a.m.