Triple

T15498411
Position Surface form Disambiguated ID Type / Status
Subject Kerch Peninsula E378882 entity
Predicate hasCity P316 FINISHED
Object Kerch E11943 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: Kerch | Statement: [Kerch Peninsula, hasCity, Kerch]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kerch
Context triple: [Kerch Peninsula, hasCity, Kerch]
  • A. Kerch chosen
    Kerch is a historic port city in eastern Crimea, strategically located on the Kerch Strait linking the Black Sea and the Sea of Azov.
  • B. Kerch Peninsula
    The Kerch Peninsula is a strategically important landform in eastern Crimea that separates the Black Sea from the Sea of Azov and hosts the city of Kerch and its surrounding historical sites.
  • C. Sevastopolskaya
    Sevastopolskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the city’s southern part.
  • D. Berdyansk
    Berdyansk is a port city in southeastern Ukraine on the northern coast of the Sea of Azov, known for its maritime trade, beaches, and resort facilities.
  • E. Simferopol–Alushta
    Simferopol–Alushta is the central mountain-crossing section of the Crimean trolleybus route that links the regional capital Simferopol with the Black Sea resort town of Alushta.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fb0aee081909db1c54349ec8492 completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff454ca0f0819088ba846a448dda2e completed May 9, 2026, 2:31 p.m.
Created at: April 10, 2026, 3:53 a.m.