Triple

T9976996
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Pereyaslav E196356 entity
Predicate locationSigned P441 FINISHED
Object Pereyaslav E81575 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: Pereyaslav | Statement: [Treaty of Pereyaslav, locationSigned, Pereyaslav]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pereyaslav
Context triple: [Treaty of Pereyaslav, locationSigned, Pereyaslav]
  • A. Pereiaslav chosen
    Pereiaslav is a historic town in central Ukraine known for its rich cultural heritage and associations with notable figures of Yiddish and Ukrainian literature.
  • B. Ochakiv
    Ochakiv is a port city in southern Ukraine on the Black Sea coast, historically significant as a strategic fortress and naval base controlling access to the Dnieper–Bug estuary.
  • C. Poltava
    Poltava is a historic city in central Ukraine known for its cultural heritage, role in Ukrainian history, and commemorations of national tragedies such as the Holodomor.
  • D. Kremenets
    Kremenets is a historic town in western Ukraine known for its rich cultural heritage and once-significant Jewish community.
  • E. Konotop
    Konotop is a historic city in northeastern Ukraine, known for the 1659 Battle of Konotop and its role as a regional railway and industrial 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_69ca82eea2b88190a0e511d21a31f386 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb84d0d3c8190b268582bb79c8973 completed April 2, 2026, 12:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23de601f0819096004bf60ffa2d2c completed April 5, 2026, 10:48 a.m.
Created at: March 30, 2026, 8:48 p.m.