Triple
T6840902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niemen |
E157569
|
entity |
| Predicate | hasMajorTributary |
P415
|
FINISHED |
| Object | Šešupė |
E623816
|
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: Šešupė | Statement: [Niemen, hasMajorTributary, Šešupė]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Šešupė Context triple: [Niemen, hasMajorTributary, Šešupė]
-
A.
Šešupė
chosen
Šešupė is a river in northeastern Europe that flows through Lithuania, Poland, and Russia before joining the Neman River.
-
B.
Bērzaune
Bērzaune is a small settlement in Latvia located close to Gaiziņkalns, the country’s highest hill.
-
C.
Ukmergė
Ukmergė is a historic town in central Lithuania known for its location along the Šventoji River and its role as a regional cultural and administrative center.
-
D.
Plungė
Plungė is a town in northwestern Lithuania that serves as an important cultural and economic center of the Samogitia region.
-
E.
Šilutė
Šilutė is a town in western Lithuania known for its location near the Nemunas River delta and its historical ties to the former East Prussian region.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b4a1f88190b4f532828697fbd8 |
completed | March 27, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c74271b9dc8190abbe3b1f9819c38f |
completed | March 28, 2026, 2:52 a.m. |
Created at: March 27, 2026, 2:19 p.m.