Triple

T3103667
Position Surface form Disambiguated ID Type / Status
Subject Siege of Perekop (1736) E64778 entity
Predicate namedAfter P63 FINISHED
Object Perekop E64777 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: Perekop | Statement: [Siege of Perekop (1736), namedAfter, Perekop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Perekop
Context triple: [Siege of Perekop (1736), namedAfter, Perekop]
  • A. Perekop chosen
    Perekop is a small settlement in northern Crimea historically known for its strategic location near the narrow land connection between the Crimean Peninsula and mainland Ukraine.
  • B. Limanowa
    Limanowa is a small town in southern Poland, located in the Lesser Poland Voivodeship, known for its historical significance and picturesque mountainous surroundings.
  • C. Perekop Bay
    Perekop Bay is a shallow inlet of the Black Sea located along the northern coast of Crimea, near the Isthmus of Perekop.
  • D. Morskie Oko
    Morskie Oko is a famous glacial lake in the Tatra Mountains of southern Poland, renowned for its scenic alpine setting and popularity as a hiking destination.
  • E. Kolberg
    Kolberg is a historic Baltic Sea port city in present-day Kołobrzeg, Poland, known for its strategic military importance and spa tourism.
  • 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_69ad857dc98481909e585dc3372e3ed5 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada26f376c8190a049399e33314d52 completed March 8, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69b203846a108190a97c30c463e119b1 completed March 12, 2026, 12:06 a.m.
Created at: March 8, 2026, 3:03 p.m.