Triple
T4744648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vilnius |
E105330
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Vilnia River |
E476821
|
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: Vilnia River | Statement: [Vilnius, locatedOnRiver, Vilnia River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vilnia River Context triple: [Vilnius, locatedOnRiver, Vilnia River]
-
A.
Vilnia River
chosen
The Vilnia River is a picturesque tributary of the Neris River in Lithuania, flowing through and giving its name to the capital city of Vilnius.
-
B.
Skvyra River
Skvyra River is a small river in Ukraine that flows through the town of Skvyra in the Kyiv region.
-
C.
Rižana River
The Rižana River is a short Slovenian river that flows through the Istrian region before emptying into the Adriatic Sea near the Gulf of Trieste.
-
D.
Nemunas River
The Nemunas River is the largest river in Lithuania, flowing through major cities like Kaunas and forming part of the country’s border before emptying into the Curonian Lagoon.
-
E.
Litava River
The Litava River is a watercourse in the South Moravian Region of the Czech Republic that flows through towns such as Slavkov u Brna before joining larger river systems.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64aa72c0819082ede0f531d75e65 |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6f979ca88190bc0128812329cb24 |
completed | March 21, 2026, 10:14 a.m. |
Created at: March 20, 2026, 1:19 p.m.