Triple

T23322819
Position Surface form Disambiguated ID Type / Status
Subject Bitlis E591200 entity
Predicate nearbyCity P350 FINISHED
Object Tatvan 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: Tatvan | Statement: [Bitlis, nearbyCity, Tatvan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tatvan
Context triple: [Bitlis, nearbyCity, Tatvan]
  • A. Tatvan chosen
    Tatvan is a town in eastern Turkey’s Bitlis Province, situated on the western shore of Lake Van and serving as a regional transport and commercial hub.
  • B. Agdash
    Agdash is a regional city in central Azerbaijan known for its agricultural economy and location near the Kura River.
  • C. Behramkale
    Behramkale is a historic village in northwestern Turkey built on the ancient site of Assos, known for its well-preserved ruins and dramatic views over the Aegean Sea.
  • D. Didgori
    Didgori is a historic site in eastern Georgia renowned as the location of the decisive 1121 battle where King David IV’s forces defeated the Seljuk Turks.
  • E. Baqura
    Baqura is a small, historically contested border area between Jordan and Israel, notable for its agricultural land and its role in the 1994 Israel–Jordan peace treaty land arrangements.
  • 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_69e25d1effe4819096907f95f610dbff completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1978731b0819090f92ef768f2a749 completed April 29, 2026, 5:30 a.m.
Created at: April 17, 2026, 5:07 p.m.