Triple
T32663532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Амгунь |
E835092
|
entity |
| Predicate | сторонаПритокаПоОтношениюКАмуру |
P114978
|
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.
tributarySide
chosen
Indicates the side (e.g., left or right bank) of a main watercourse on which a tributary joins it.
-
B.
sidesWith
Indicates that one entity aligns with, supports, or takes the same position as another entity in a conflict, dispute, or decision.
-
C.
hasTributaryRelationsWith
Indicates that one entity maintains a tributary relationship with another, typically involving regular payments or offerings in exchange for protection, favor, or acknowledgment of superiority.
-
D.
A-sideOf
Indicates that one entity is located on or corresponds to the A-side (first or primary side) of another entity, typically in a two-sided context.
-
E.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
- 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_69f6c7a66d3881908f5aec4ccd11d60d |
completed | May 3, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.