Triple

T31011485
Position Surface form Disambiguated ID Type / Status
Subject Bağçasaray E790218 entity
Predicate hasSecondaryLanguageCurrently P9103 FINISHED
Object Russian LITERAL 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: Russian | Statement: [Bağçasaray, hasSecondaryLanguageCurrently, Russian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecondaryLanguageCurrently
Context triple: [Bağçasaray, hasSecondaryLanguageCurrently, Russian]
  • A. hasSecondaryLanguage chosen
    Indicates that an entity possesses or uses a secondary language in addition to its primary language.
  • B. hasSecondaryLanguageNearby
    Indicates that an entity has at least one secondary language present or used in its immediate vicinity or surrounding context.
  • C. hasSecondaryLanguageFamily
    Indicates that an entity has an additional, non-primary association with a particular language family.
  • D. hasSecondaryNationalLanguage
    Indicates that an entity possesses an officially recognized secondary national language in addition to its primary national language.
  • E. hasSecondaryLanguageTradition
    Indicates that an entity possesses an additional, non-primary language tradition associated with it, such as in its use, documentation, or cultural context.
  • F. None of above.

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_69f224c73ca48190a1e46cb58ad4045b completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fed357b2b4819084c709056a54461f completed May 9, 2026, 6:25 a.m.
PD Predicate disambiguation batch_69fed103d9cc81909b11619745110c61 completed May 9, 2026, 6:15 a.m.
Created at: April 29, 2026, 8:57 p.m.