Triple
T8029622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltiysk |
E186943
|
entity |
| Predicate | positionOnSea |
P66108
|
FINISHED |
| Object | westernmost port of Russia on the Baltic Sea |
—
|
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: westernmost port of Russia on the Baltic Sea | Statement: [Baltiysk, positionOnSea, westernmost port of Russia on the Baltic Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnSea Context triple: [Baltiysk, positionOnSea, westernmost port of Russia on the Baltic Sea]
-
A.
oceanLocation
chosen
Indicates that one entity is geographically located in, on, or adjacent to a particular ocean.
-
B.
positionRelativeToCoast
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
C.
isSeawardOf
Indicates that one location lies closer to or toward the sea relative to another location.
-
D.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
E.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ecf0f2c819091899211003c461e |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.