Triple
T13522305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kavkaz |
E322927
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Port Krym |
E11943
|
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: Port Krym | Statement: [Kavkaz, connectsTo, Port Krym]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Port Krym Context triple: [Kavkaz, connectsTo, Port Krym]
-
A.
Port Pivdennyi
Port Pivdennyi is a major deep-water seaport on Ukraine’s Black Sea coast, serving as a key hub for bulk cargo and international maritime trade.
-
B.
Odesa harbor
Odesa harbor is a major Black Sea port of Ukraine, serving as a key hub for maritime trade, passenger traffic, and naval activity for the city of Odesa.
-
C.
Kerch
chosen
Kerch is a historic port city in eastern Crimea, strategically located on the Kerch Strait linking the Black Sea and the Sea of Azov.
-
D.
Simferopol–Alushta
Simferopol–Alushta is the central mountain-crossing section of the Crimean trolleybus route that links the regional capital Simferopol with the Black Sea resort town of Alushta.
-
E.
Skadovsk Port
Skadovsk Port is a Ukrainian seaport on the Black Sea that serves as a regional maritime hub for cargo and passenger transport in Kherson Oblast.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa535cc81908d0018fef81a2848 |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75d93a2608190a3a693bf4086a010 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.