Triple

T11443073
Position Surface form Disambiguated ID Type / Status
Subject Yeysk Local History Museum E271192 entity
Predicate regionServed P82 FINISHED
Object Yeysk E55933 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: Yeysk | Statement: [Yeysk Local History Museum, regionServed, Yeysk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yeysk
Context triple: [Yeysk Local History Museum, regionServed, Yeysk]
  • A. Yeysk chosen
    Yeysk is a Russian port town and resort on the Sea of Azov, known for its beaches, shallow waters, and role as a regional fishing and shipping center.
  • B. Ozerki
    Ozerki is a locality in Russia historically noted as the site where the revolutionary priest Georgy Gapon was killed.
  • C. Yenakiieve
    Yenakiieve is an industrial city in eastern Ukraine, historically known for its coal mining and metallurgical industries.
  • D. Ksudach
    Ksudach is a large stratovolcano in Russia’s Kamchatka Peninsula known for its caldera-forming eruptions and remote, rugged landscape.
  • E. Yèvre
    Yèvre is a river in central France that flows through the Cher department and serves as one of its notable waterways.
  • 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_69d6aadff8888190a13f253f0d460874 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d808891b7481908bf5a80cb7644061 completed April 9, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69ee866bb71c819091573965f7cf0dee completed April 26, 2026, 9:40 p.m.
Created at: April 8, 2026, 9:35 p.m.