Triple
T26401174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panemunė, Lithuania |
E663700
|
entity |
| Predicate | riverFormsBorder |
P31306
|
FINISHED |
| Object | Neman River |
—
|
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: Neman River | Statement: [Panemunė, Lithuania, riverFormsBorder, Neman River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverFormsBorder Context triple: [Panemunė, Lithuania, riverFormsBorder, Neman River]
-
A.
riverFormsBorderWith
chosen
Indicates that a river serves as a boundary line between two geographic or political entities.
-
B.
formsBorderWithin
Indicates that one entity constitutes a boundary or border located entirely within the spatial extent of another entity.
-
C.
flowsAlongBorderWith
Indicates that something, typically a fluid or current, moves in a path that runs adjacent to and follows the boundary shared with another entity.
-
D.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
E.
hasWaterBorderWith
Indicates that two entities share a common boundary that runs along or across a body of water, such as a river, lake, or sea.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 26, 2026, 11:32 p.m.