Triple
T3329226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodosia |
E69993
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Feodosia Bay |
E65917
|
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: Feodosia Bay | Statement: [Theodosia, locatedOn, Feodosia Bay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feodosia Bay Context triple: [Theodosia, locatedOn, Feodosia Bay]
-
A.
Nagaev Bay
Nagaev Bay is a coastal inlet of the Sea of Okhotsk in Russia’s Far East, serving as the main harbor area for the port city of Magadan.
-
B.
Mezen Bay
Mezen Bay is a large, remote inlet in the southeastern White Sea of northwestern Russia, known for its extreme tidal ranges and harsh Arctic coastal environment.
-
C.
Perekop Bay
chosen
Perekop Bay is a shallow inlet of the Black Sea located along the northern coast of Crimea, near the Isthmus of Perekop.
-
D.
Tsemess Bay
Tsemess Bay is a natural harbor on Russia’s Black Sea coast, known for hosting the major port city of Novorossiysk and serving as an important maritime and industrial hub.
-
E.
Dvina Bay
Dvina Bay is a large inlet of the White Sea in northwestern Russia, known for its connection to the Northern Dvina River and the port city of Arkhangelsk.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1708b908190bc5c4122623d9b77 |
completed | March 8, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a7ec9f48190873d90b678713bad |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:12 p.m.