Triple

T151556
Position Surface form Disambiguated ID Type / Status
Subject Russian Black Sea Fleet E3441 entity
Predicate hasBase P2909 FINISHED
Object Feodosia E12601 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 | Statement: [Russian Black Sea Fleet, hasBase, Feodosia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Feodosia
Context triple: [Russian Black Sea Fleet, hasBase, Feodosia]
  • A. Feodosia chosen
    Feodosia is a historic port city on the southeastern coast of Crimea, known for its Black Sea beaches, medieval fortifications, and association with painter Ivan Aivazovsky.
  • B. Sevastopol
    Sevastopol is a major port city on the Black Sea, historically significant as a naval base and the site of key military conflicts.
  • C. Simferopol
    Simferopol is the administrative and cultural center of Crimea, known as a key regional hub for transportation, education, and industry.
  • 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. Novorossiysk
    Novorossiysk is a major port city on Russia’s Black Sea coast that serves as an important naval and commercial hub.
  • 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_69a252868de4819080e21c9938bfe8b6 completed Feb. 28, 2026, 2:27 a.m.
NER Named-entity recognition batch_69a25bab43608190ba5ebfbee6b5b6e4 completed Feb. 28, 2026, 3:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69a36ceb0244819092fdbbd095804b83 completed Feb. 28, 2026, 10:32 p.m.
Created at: Feb. 28, 2026, 2:31 a.m.