Triple
T28064863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шилка |
E709217
|
entity |
| Predicate | тип водотока |
P27890
|
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.
typeOfWaterfall
Indicates that one entity is a specific kind or category of waterfall in relation to another entity.
-
C.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
D.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
-
E.
hasWatercourseType
chosen
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
- 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_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:42 p.m.