Triple

T19840317
Position Surface form Disambiguated ID Type / Status
Subject Asenovgrad E476708 entity
Predicate formerName P65 FINISHED
Object Stanimaka 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: Stanimaka | Statement: [Asenovgrad, formerName, Stanimaka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stanimaka
Context triple: [Asenovgrad, formerName, Stanimaka]
  • A. Stanimaka chosen
    Stanimaka is the former name of Asenovgrad, a historic town in southern Bulgaria known for its medieval fortress and numerous churches.
  • B. Tihomir
    Tihomir is a masculine given name of Slavic origin, commonly used in several countries of the Balkans.
  • C. Kudirka
    Kudirka is a Lithuanian surname most notably borne by Vincas Kudirka, the author of Lithuania’s national anthem and a key figure in the Lithuanian national revival.
  • D. Stalać
    Stalać is a village in central Serbia known for its strategic location near the confluence of major rivers and important transportation routes.
  • E. Kunigal
    Kunigal is a town in the Tumakuru district of Karnataka, India, known for its proximity to Markonahalli Dam and its agricultural surroundings.
  • 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_69d8e51d39d081909bcfafeaaf3d2fcc completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6580576748190b85e234b01209ae7 completed April 20, 2026, 4:44 p.m.
Created at: April 10, 2026, 1:50 p.m.