Triple
T14315401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Bug River |
E354942
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Savran River |
E526231
|
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: Savran River | Statement: [Southern Bug River, hasTributary, Savran River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Savran River Context triple: [Southern Bug River, hasTributary, Savran River]
-
A.
Savran River
chosen
The Savran River is a minor watercourse in southwestern Ukraine that serves as one of the tributaries feeding into the Southern Bug River system.
-
B.
Vedea River
The Vedea River is a river in southern Romania that flows through several counties before emptying into the Danube.
-
C.
Ikorets River
The Ikorets River is a smaller watercourse in western Russia that serves as a tributary within the Voronezh River basin.
-
D.
Berheci River
The Berheci River is a watercourse in eastern Romania that serves as a tributary of the Bârlad River, flowing through rural areas and contributing to the region’s drainage basin.
-
E.
Harnav River
Harnav River is a smaller river in western India that serves as one of the tributaries feeding into the Sabarmati River system.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8838e45c819080ee69dd39e3bd43 |
completed | April 14, 2026, 6:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00077201c08190a0c3bb259856d5c9 |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:12 a.m.