Triple

T19314494
Position Surface form Disambiguated ID Type / Status
Subject Atabegs of Samtskhe E483059 entity
Predicate title P38 FINISHED
Object atabeg 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: atabeg | Statement: [Atabegs of Samtskhe, title, atabeg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: atabeg
Context triple: [Atabegs of Samtskhe, title, atabeg]
  • A. Beg chosen
    Beg is a historical Turkic and Central Asian noble title denoting a chieftain, lord, or high-ranking official.
  • B. Begnins
    Begnins is a small municipality in the canton of Vaud in western Switzerland, situated in the La Côte wine-growing region between Lake Geneva and the Jura Mountains.
  • C. Begil
    Begil is a heroic figure from Turkic epic tradition, known as the central protagonist in the tale of Begil Oglu Emren Boyu.
  • D. BEG
    BEG is the IATA airport code for Belgrade Nikola Tesla Airport, the main international airport serving Serbia’s capital city.
  • E. begenna
    The begenna is a large Ethiopian box-lyre, especially associated with Amhara religious and devotional music, often referred to as the "Harp of David."
  • 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604cfec8c8190a118b327b1418150 completed April 20, 2026, 10:49 a.m.
Created at: April 10, 2026, 1:32 p.m.