Triple
T28064861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шилка |
E709217
|
entity |
| Predicate | образует реку совместно с |
P11843
|
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.
closelyAssociatedRiver
Indicates a river that is geographically or functionally closely connected to the subject, such as flowing nearby, through, or otherwise strongly linked to it.
-
B.
riverFormed
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
C.
riverConfluence
chosen
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
D.
operatesOnRiver
Indicates that an entity conducts its operations or activities on, along, or directly involving a river.
-
E.
mainRiverAssociated
Indicates that one entity is associated with, or primarily linked to, a particular main river.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6401a0a048190acce63aa4eceffac |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:42 p.m.