Triple
T11161882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yantra River |
E264055
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Lomya River |
E444954
|
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: Lomya River | Statement: [Yantra River, hasTributary, Lomya River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lomya River Context triple: [Yantra River, hasTributary, Lomya River]
-
A.
Lomya River
chosen
The Lomya River is a lesser-known river that serves as a tributary within the Yantra River basin in Bulgaria.
-
B.
Kasplya River
The Kasplya River is a tributary waterway in Eastern Europe that feeds into the larger Daugava River system.
-
C.
Khudosey River
The Khudosey River is a significant watercourse in northern Siberia, Russia, known as one of the main tributaries contributing to the Taz River basin.
-
D.
Chermyanka River
The Chermyanka River is a small river in Moscow, Russia, that flows through the city’s northeastern districts before joining the Yauza River.
-
E.
Sakmara River
The Sakmara River is a major river in Russia that flows through the southern Ural region before joining the Ural 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8832fe88190a74d81f9ed547baa |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d6d4bd8819087902472e77e0d38 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 8, 2026, 9:29 p.m.