Triple

T11750031
Position Surface form Disambiguated ID Type / Status
Subject JRV E279380 entity
Predicate usedLanguage P741 FINISHED
Object Serbo-Croatian E219480 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: Serbo-Croatian | Statement: [JRV, usedLanguage, Serbo-Croatian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Serbo-Croatian
Context triple: [JRV, usedLanguage, Serbo-Croatian]
  • A. Serbo-Croatian chosen
    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.
  • B. Serbian language
    The Serbian language is a South Slavic language primarily spoken in Serbia and neighboring regions, using both Cyrillic and Latin scripts.
  • C. Bosnian
    Bosnian is a South Slavic language primarily spoken in Bosnia and Herzegovina and by Bosniak communities in the Balkans and worldwide.
  • D. Shtokavian dialect
    The Shtokavian dialect is the South Slavic dialectal base from which the standard forms of Bosnian, Croatian, Serbian, and Montenegrin developed.
  • E. Croatian
    Croatian is a South Slavic language primarily spoken in Croatia and recognized as one of the official languages of the European Union.
  • 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_69d6ab01038c819080714901502c84fc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a508b0c4819082fbcc27d559ea2f completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f01a13550081909a26f57b30d68e03 completed April 28, 2026, 2:23 a.m.
Created at: April 8, 2026, 9:41 p.m.