Triple
T24909936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шешупе |
E623818
|
entity |
| Predicate | длинаВРоссии |
P157865
|
FINISHED |
| Object | ~116 км |
—
|
LITERAL 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: ~116 км | Statement: [Шешупе, длинаВРоссии, ~116 км]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: длинаВРоссии Context triple: [Шешупе, длинаВРоссии, ~116 км]
-
A.
длинаВЛитве
Indicates a relationship where a specified length is measured or defined within the context of Lithuania (e.g., according to Lithuanian standards, territory, or infrastructure).
-
B.
strengthRussia
Indicates a relationship where a level, measure, or display of strength is attributed to or associated with Russia.
-
C.
rankInRussiaByArea
Indicates the position of an entity in an ordered list of entities in Russia sorted by their area size.
-
D.
distanceToRussianBorder_km
Indicates the physical distance, measured in kilometers, between a given location and the nearest point on the Russian border.
-
E.
distanceToVladivostok_km
Indicates the physical distance, measured in kilometers, between a given location and Vladivostok.
- F. None of above. chosen
Provenance (4 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_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 5:27 a.m.