Triple

T19264311
Position Surface form Disambiguated ID Type / Status
Subject Bijela E481729 entity
Predicate languageUsed P238 FINISHED
Object Serbian 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: Serbian | Statement: [Bijela, languageUsed, Serbian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Serbian
Context triple: [Bijela, languageUsed, Serbian]
  • A. Serbian language chosen
    The Serbian language is a South Slavic language primarily spoken in Serbia and neighboring regions, using both Cyrillic and Latin scripts.
  • B. Serbo-Croatian
    Serbo-Croatian is a South Slavic language historically spoken across the former Yugoslavia, encompassing the standardized varieties now known as Serbian, Croatian, Bosnian, and Montenegrin.
  • C. Montenegrin
    Montenegrin is a South Slavic language spoken primarily in Montenegro and recognized as one of the standard varieties of the Serbo-Croatian language continuum.
  • D. Serbian Wikisource
    Serbian Wikisource is the Serbian-language edition of Wikisource, a free online digital library of public domain and freely licensed texts.
  • E. Old Serbian
    Old Serbian is a historical South Slavic language variety used in medieval Serbia, particularly in royal, legal, and religious documents.
  • 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_69d8e8ce54cc8190998418ff1f66ef28 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fb8bce6881908395836960762672 completed April 20, 2026, 10:10 a.m.
Created at: April 10, 2026, 1:28 p.m.