Triple
T24909943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шешупе |
E623818
|
entity |
| Predicate | впадаетВРекуНаТерритории |
P86882
|
FINISHED |
| Object | Литва |
—
|
NE NERFINISHED |
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: Литва | Statement: [Шешупе, впадаетВРекуНаТерритории, Литва]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: впадаетВРекуНаТерритории Context triple: [Шешупе, впадаетВРекуНаТерритории, Литва]
-
A.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
B.
isWatercourseOf
chosen
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
тип реки
Indicates the classification or category of a river based on its characteristics or role.
-
E.
reservoirRiver
Indicates that a reservoir is supplied or drained by, and thus hydrologically connected to, a particular river.
- F. None of above.
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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:27 a.m.