Triple
T1575102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalta Embankment |
E33630
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Yalta bay |
E33631
|
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 bay | Statement: [Yalta Embankment, hasViewOf, Yalta bay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yalta bay Context triple: [Yalta Embankment, hasViewOf, Yalta bay]
-
A.
Yalta Bay
chosen
Yalta Bay is a coastal inlet on the southern shore of the Crimean Peninsula, forming the maritime setting for the resort city of Yalta on the Black Sea.
-
B.
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.
-
C.
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.
-
D.
Perekop Bay
Perekop Bay is a shallow inlet of the Black Sea located along the northern coast of Crimea, near the Isthmus of Perekop.
-
E.
Neva Bay
Neva Bay is a shallow eastern extension of the Gulf of Finland near Saint Petersburg, Russia, serving as the receiving basin for the Neva River before it enters the Baltic Sea.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a908d2cffc819090f3d5cbebae3307 |
completed | March 5, 2026, 4:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad4696c34c8190826bc6ab4dad7c01 |
completed | March 8, 2026, 9:51 a.m. |
Created at: March 4, 2026, 7:27 p.m.