Triple

T16927157
Position Surface form Disambiguated ID Type / Status
Subject Bug Estuary E410603 entity
Predicate nearCity P350 FINISHED
Object Mykolaiv NE NERFINISHED

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: Mykolaiv | Statement: [Bug Estuary, nearCity, Mykolaiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mykolaiv
Context triple: [Bug Estuary, nearCity, Mykolaiv]
  • A. Mykolaiv chosen
    Mykolaiv is a major shipbuilding and industrial city in southern Ukraine located near the Black Sea.
  • B. Kherson
    Kherson is a port city in southern Ukraine near the Black Sea, historically significant as a shipbuilding and industrial center and strategically important due to its location on the Dnieper River.
  • C. Kryvyi Rih
    Kryvyi Rih is a major industrial city in central Ukraine known for its extensive iron ore mining and steel production.
  • D. Odesa
    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.
  • E. Oleksandriia
    Oleksandriia is a city in central Ukraine known as an industrial and transport hub within the Kirovohrad region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cdf2dcd881909798bd245e18c599 completed April 18, 2026, 6:31 p.m.
Created at: April 10, 2026, 5:30 a.m.