Triple
T15113998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guria |
E360987
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Bzhuzhi River |
E445769
|
NE 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: Bzhuzhi River | Statement: [Guria, hasRiver, Bzhuzhi River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bzhuzhi River Context triple: [Guria, hasRiver, Bzhuzhi River]
-
A.
Bzhuzhi River
chosen
The Bzhuzhi River is a regional waterway in western Georgia that flows through the area of Ozurgeti in the Guria region.
-
B.
Chorokhi River
The Chorokhi River is a significant waterway in southwestern Georgia and northeastern Turkey that flows through mountainous terrain before emptying into the Black Sea near the city of Batumi.
-
C.
Bori River
The Bori River is a smaller river in central India that feeds into the larger Tapti River system.
-
D.
Pchyovzha River
The Pchyovzha River is a smaller watercourse in northwestern Russia that serves as one of the tributaries feeding into the Volkhov River system.
-
E.
Khrami River
The Khrami River is a significant river in the South Caucasus that flows through Georgia and Azerbaijan before joining the Mtkvari (Kura) River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058f4fb88190a3d446a466aebcf1 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ec19c508190912c3fe186f8a992 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 3:05 a.m.