Triple
T10587845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Berdyansk |
E249900
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Berdyansk |
E72642
|
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: Berdyansk | Statement: [Port of Berdyansk, nearbyCity, Berdyansk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berdyansk Context triple: [Port of Berdyansk, nearbyCity, Berdyansk]
-
A.
Berdyansk
chosen
Berdyansk is a port city in southeastern Ukraine on the northern coast of the Sea of Azov, known for its maritime trade, beaches, and resort facilities.
-
B.
Rostov-on-Don
Rostov-on-Don is a major port city in southern Russia, located on the Don River near the Sea of Azov and serving as an important administrative, cultural, and industrial center of the region.
-
C.
Novocherkassk
Novocherkassk is a historic city in Russia’s Rostov Oblast that served as a key Cossack and military administrative center.
-
D.
Krasnovodsk
Krasnovodsk, now known as Türkmenbaşy, is a key port city on the eastern shore of the Caspian Sea in western Turkmenistan.
-
E.
Zheleznovodsk
Zheleznovodsk is a spa town in Russia’s Stavropol Krai, known for its mineral springs and health resorts in the Caucasus region.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d527793c588190bfe3a5261eb7f919 |
completed | April 7, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e23b1c5e4c81909628c77b80805353 |
completed | April 17, 2026, 1:52 p.m. |
Created at: April 6, 2026, 12:40 p.m.