Triple
T24909944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шешупе |
E623818
|
entity |
| Predicate | пересекаетГраницу |
P13760
|
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.
crossesBorderOf
chosen
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
B.
crossedBoundary
Indicates that an entity has moved from one defined area, region, or limit into another, thereby passing across a specified boundary.
-
C.
crossesInternationalBoundaryAt
Indicates that one entity passes from one country’s territory into another at a specific boundary location.
-
D.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
E.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
- 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_69f4236e93c081908876aff0a06ed21a |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.