Triple

T21352919
Position Surface form Disambiguated ID Type / Status
Subject Ivan Starov E526534 entity
Predicate notableWork P4 FINISHED
Object Urban plan of 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: Urban plan of Mykolaiv | Statement: [Ivan Starov, notableWork, Urban plan of Mykolaiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Urban plan of Mykolaiv
Context triple: [Ivan Starov, notableWork, Urban plan of Mykolaiv]
  • A. Mykolaiv chosen
    Mykolaiv is a major shipbuilding and industrial city in southern Ukraine located near the Black Sea.
  • B. Oleksandriia
    Oleksandriia is a city in central Ukraine known as an industrial and transport hub within the Kirovohrad region.
  • C. Myrhorod
    Myrhorod is a historic city in central Ukraine, known for its mineral springs and as the setting of several stories by writer Nikolai Gogol.
  • D. Kremenchuk
    Kremenchuk is an industrial city in central Ukraine on the Dnieper River, historically significant as a major transport and strategic hub.
  • E. Melitopol
    Melitopol is a strategically important industrial and transportation hub in southeastern Ukraine, known for its agricultural production and key road and rail connections.
  • 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8ad34a1d48190b14fa099968faf7c completed April 22, 2026, 11:12 a.m.
Created at: April 16, 2026, 5:05 p.m.