Triple
T34931160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Navy gunboat Berdyansk |
E1007437
|
entity |
| Predicate | associatedStrait |
P21880
|
FINISHED |
| Object | Kerch Strait |
E56900
|
NE 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: Kerch Strait | Statement: [Ukrainian Navy gunboat Berdyansk, associatedStrait, Kerch Strait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStrait Context triple: [Ukrainian Navy gunboat Berdyansk, associatedStrait, Kerch Strait]
-
A.
hasStrategicStrait
Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
-
B.
isNorthernmostStraitOf
Indicates that one strait is the furthest north among all straits associated with a particular geographic feature or region.
-
C.
hasStrait
Indicates that there is a strait—a narrow body of water—connecting or lying between the two referenced geographic entities.
-
D.
straitNamedAfter
Indicates that a strait bears a name derived from or in honor of a particular entity.
-
E.
nearbyStrait
chosen
Indicates that one entity is located close to or adjacent to a particular strait.
- F. None of above.
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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b26447cc8190a75dcc83b3110ef5 |
completed | June 21, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.