Triple

T3408423
Position Surface form Disambiguated ID Type / Status
Subject Mount Mithridat E71831 entity
Predicate viewIncludes P17987 FINISHED
Object Kerch port 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 port | Statement: [Mount Mithridat, viewIncludes, Kerch port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kerch port
Context triple: [Mount Mithridat, viewIncludes, Kerch port]
  • 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 Strait
    The Kerch Strait is a narrow waterway connecting the Black Sea and the Sea of Azov, strategically important as a maritime passage between Eastern Europe and the Caucasus.
  • C. Sevastopolskaya
    Sevastopolskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the city’s southern part.
  • D. Port of Berdyansk
    The Port of Berdyansk is a key commercial seaport on the northern coast of the Sea of Azov, serving as an important maritime gateway for regional trade and industry.
  • E. Kursk
    Kursk is a historic city in western Russia known for the pivotal World War II Battle of Kursk and its role as an important regional industrial and cultural center.
  • 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_69ad85ac312481909e7027ced1456a9f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb9056acc8190a9c50ec374851ac8 completed March 8, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69b360be3b6c81909ee0ac6d4512a56d completed March 13, 2026, 12:56 a.m.
Created at: March 8, 2026, 3:15 p.m.