Triple

T12550359
Position Surface form Disambiguated ID Type / Status
Subject Komotini E300079 entity
Predicate languageUsed P238 FINISHED
Object Pomak E649247 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: Pomak | Statement: [Komotini, languageUsed, Pomak]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pomak
Context triple: [Komotini, languageUsed, Pomak]
  • A. Pomaks chosen
    Pomaks are a Slavic Muslim ethnic group primarily living in Bulgaria and neighboring Balkan regions, known for speaking a Bulgarian dialect and preserving distinct religious and cultural traditions.
  • B. Pomarance
    Pomarance is a historic Tuscan town in central Italy, known for its medieval architecture and proximity to the geothermal area of Larderello.
  • C. Pavica
    Pavica is a feminine given name of South Slavic origin, commonly used as a diminutive form of the name Pavao.
  • D. Goranci
    Goranci is an alternative name for the Avromani people, a small ethnic group traditionally inhabiting parts of the Balkans.
  • E. Pantchoulidzew
    Pantchoulidzew is the surname of Alexis Pantchoulidzew, a historical figure of likely Eastern European or Russian origin.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95482c1348190b6f964decef5cc0a completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f655853ecc8190b178a489d806a0c4 completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 9:58 p.m.