Triple

T13045264
Position Surface form Disambiguated ID Type / Status
Subject Turkish Wall at Perekop E327301 entity
Predicate nearbySettlement P350 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: [Turkish Wall at Perekop, nearbySettlement, Perekop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Perekop
Context triple: [Turkish Wall at Perekop, nearbySettlement, 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. Żory
    Żory is a city in southern Poland known for its historical roots in the Silesian region and its mix of industrial and residential character.
  • C. Serock
    Serock is a locality situated near the Western Bug River in eastern Europe.
  • D. Limanowa
    Limanowa is a small town in southern Poland, located in the Lesser Poland Voivodeship, known for its historical significance and picturesque mountainous surroundings.
  • E. Malew
    Malew is a parish on the Isle of Man that includes the area around Ronaldsway and its airport.
  • 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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d98050157c8190bb8c640b759ac2b7 completed April 10, 2026, 10:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6ead25b7c8190af2ccf26b44c2ea2 completed May 3, 2026, 6:27 a.m.
Created at: April 9, 2026, 8:56 p.m.