Triple
T257225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalta |
E5461
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Yalta Commercial Sea Port |
E33129
|
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: Yalta Commercial Sea Port | Statement: [Yalta, hasPort, Yalta Commercial Sea Port]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yalta Commercial Sea Port Context triple: [Yalta, hasPort, Yalta Commercial Sea Port]
-
A.
Yalta Sea Port
chosen
Yalta Sea Port is a major maritime harbor and transportation hub serving the resort city of Yalta on the southern coast of the Crimean Peninsula.
-
B.
Nakhodka
Nakhodka is a key port city on Russia’s Pacific coast, serving as an important hub for maritime trade and transport in the Russian Far East.
-
C.
Sevastopol
Sevastopol is a major port city on the Black Sea, historically significant as a naval base and the site of key military conflicts.
-
D.
Kerch
Kerch is a historic port city in eastern Crimea, strategically located on the Kerch Strait linking the Black Sea and the Sea of Azov.
-
E.
Novorossiysk
Novorossiysk is a major port city on Russia’s Black Sea coast that serves as an important naval and commercial hub.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d5884c88190a349d7593b688921 |
completed | Feb. 28, 2026, 3:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3914d5cd08190bd755e1e65feee2a |
completed | March 1, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.