Triple
T5522198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyatka |
E144836
|
entity |
| Predicate | hasNameOrigin |
P3325
|
FINISHED |
| Object | Vyatka River |
E321320
|
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: Vyatka River | Statement: [Vyatka, hasNameOrigin, Vyatka River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vyatka River Context triple: [Vyatka, hasNameOrigin, Vyatka River]
-
A.
Vyatka River
chosen
The Vyatka River is a major river in western Russia that flows through the Kirov and Nizhny Novgorod regions and plays an important role in regional transport, ecology, and settlement.
-
B.
Kostroma River
The Kostroma River is a major waterway in central Russia that flows through Kostroma Oblast before joining the Volga River.
-
C.
Okhta River
The Okhta River is a tributary waterway in northwestern Russia that flows through Saint Petersburg before joining the Neva River.
-
D.
Votka River
The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
-
E.
Byk River
The Byk River is a tributary watercourse in Eastern Europe that flows through Moldova before joining the Dniester 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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f73cc8c8190a92a839c1ca804c7 |
completed | March 22, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b08225f08190ac27f066573b4f28 |
completed | March 23, 2026, 3:16 a.m. |
Created at: March 22, 2026, 3:33 p.m.