Triple

T9527392
Position Surface form Disambiguated ID Type / Status
Subject Shirin E229793 entity
Predicate hasVariantInLanguage P64249 FINISHED
Object Turkish 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: Turkish | Statement: [Shirin, hasVariantInLanguage, Turkish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVariantInLanguage
Context triple: [Shirin, hasVariantInLanguage, Turkish]
  • A. hasVariant
    Indicates that one entity exists as an alternative form, version, or variation of another entity.
  • B. languageOfVariant chosen
    Indicates that one entity is the language in which a particular variant or version of another entity is expressed.
  • C. languageVariant
    Indicates that one language is a variant, dialect, or localized form of another language.
  • D. hasLinguisticVariety
    Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
  • E. linguisticVariant
    Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language 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_69ca8479934c81908006d0e6e970ae05 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd989c831081908877e42f7ead84ba completed April 1, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69cca56c44f88190a54a5d2a133bb07e completed April 1, 2026, 4:56 a.m.
Created at: March 30, 2026, 8 p.m.