Triple
T1560373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sochi |
E33306
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Sochi seaport |
E33306
|
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: Sochi seaport | Statement: [Sochi, hasPort, Sochi seaport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sochi seaport Context triple: [Sochi, hasPort, Sochi seaport]
-
A.
Yalta Sea Port
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.
Novorossiysk
Novorossiysk is a major port city on Russia’s Black Sea coast that serves as an important naval and commercial hub.
-
C.
Gelendzhik
Gelendzhik is a Black Sea resort city in southern Russia known for its beaches, scenic bay, and tourism infrastructure.
-
D.
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.
-
E.
Sochi
chosen
Sochi is a Russian resort city on the Black Sea coast, known for its subtropical climate, beaches, and as the host of the 2014 Winter Olympics.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90885d6208190b4b7d6ad336d4d16 |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad3712e2ac81908c66f18fa89d46f2 |
completed | March 8, 2026, 8:45 a.m. |
Created at: March 4, 2026, 7:27 p.m.