Triple
T23953066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шхара |
E603101
|
entity |
| Predicate | дренируетсяРекой |
P76010
|
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.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
B.
drainsAreaOf
Indicates that one entity serves as a drainage outlet or basin for another entity, carrying away its surface or groundwater.
-
C.
hasBodyOfWaterDrainedBy
chosen
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
-
D.
drainedIn
Indicates that a liquid, resource, or substance has flowed out from one entity and been discharged or emptied into another entity or location.
-
E.
drainageOutlet
Indicates that one entity serves as the point where fluids or runoff are discharged or exit from another 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.