Triple

T1825869
Position Surface form Disambiguated ID Type / Status
Subject Battleship Potemkin E40650 entity
Predicate setting P1957 FINISHED
Object Odessa E38290 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: Odessa | Statement: [Battleship Potemkin, setting, Odessa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Odessa
Context triple: [Battleship Potemkin, setting, Odessa]
  • A. Odesa chosen
    Odesa is a major port city on the Black Sea in southern Ukraine, known for its historic architecture, multicultural heritage, and key economic and cultural role in the country.
  • B. Kryvyi Rih
    Kryvyi Rih is a major industrial city in central Ukraine known for its extensive iron ore mining and steel production.
  • C. Mykolaiv
    Mykolaiv is a major shipbuilding and industrial city in southern Ukraine located near the Black Sea.
  • D. Dnipro
    Dnipro is one of Ukraine’s largest industrial and cultural centers, located on the Dnieper River in the central-eastern part of the country.
  • E. Kharkiv
    Kharkiv is Ukraine’s second-largest city and a major industrial, cultural, and educational center in the northeast of the country.
  • 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_69a8864644bc8190b2358ab897194ac1 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb00f13888190aa5582263d55d371 completed March 7, 2026, 4:56 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae8929b30c8190b21f16bcb6225406 completed March 9, 2026, 8:47 a.m.
Created at: March 4, 2026, 7:32 p.m.