Triple

T18376722
Position Surface form Disambiguated ID Type / Status
Subject Oltu stone E446336 entity
Predicate marketedAs P1395 FINISHED
Object Erzurum Oltu taşı NE NERFINISHED

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: Erzurum Oltu taşı | Statement: [Oltu stone, marketedAs, Erzurum Oltu taşı]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erzurum Oltu taşı
Context triple: [Oltu stone, marketedAs, Erzurum Oltu taşı]
  • A. Erzurum stone chosen
    Erzurum stone is a type of jet-like black gemstone traditionally mined and crafted in the Oltu district of Erzurum, Turkey, renowned for its use in jewelry and prayer beads.
  • B. Erzurum Castle
    Erzurum Castle is a historic fortress in the city of Erzurum in eastern Turkey, notable for its strategic hilltop location and centuries-old defensive architecture.
  • C. Gökdepe
    Gökdepe is a historic town in southern Turkmenistan known for the 1881 Battle of Geok Tepe between Russian imperial forces and Turkmen defenders.
  • D. Savaştepe
    Savaştepe is a town and district in western Turkey, located within the Marmara Region.
  • E. Çiçekdağı
    Çiçekdağı is a town and district in central Turkey known for its rural Anatolian character within Kırşehir Province.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e5179849d08190a3ffb9edc633d2ee completed April 19, 2026, 5:57 p.m.
Created at: April 10, 2026, 10:45 a.m.