Triple
T11196865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubna |
E264944
|
entity |
| Predicate | twinnedWith |
P1072
|
FINISHED |
| Object | Alushta |
E67783
|
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: Alushta | Statement: [Dubna, twinnedWith, Alushta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alushta Context triple: [Dubna, twinnedWith, Alushta]
-
A.
Alushta
chosen
Alushta is a resort town on the southern coast of Crimea, known for its beaches, mild climate, and role as a popular Black Sea tourist destination.
-
B.
Liman
Liman is a surname most notably associated with American film director and producer Doug Liman.
-
C.
Vineta
Vineta is a legendary medieval Baltic Sea trading city, often associated with the island of Wolin and famed in myth as a wealthy metropolis lost beneath the waves.
-
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.
Obdorsk
Obdorsk is the historical name of the Arctic city now known as Salekhard in northwestern Siberia, Russia.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c082fc8190866c574f698b59ef |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4840640688190a5b3c36883b8fce8 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 8, 2026, 9:29 p.m.