Triple
T24909947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шешупе |
E623818
|
entity |
| Predicate | частичноЯвляетсяГраницей |
P96756
|
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.
partlyFormsBorderBetween
chosen
Indicates that one entity constitutes only a portion of the boundary separating two other entities.
-
B.
isPartOfLargerBoundary
Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
-
C.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
D.
formsPartOfBorderType
Indicates that one border type constitutes a component or segment of another, more comprehensive border type.
-
E.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
- 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.