Triple

T14897279
Position Surface form Disambiguated ID Type / Status
Subject Sultan Ahmad Mirza E359909 entity
Predicate languageSphere P29819 FINISHED
Object Turko-Mongol and Persian cultural sphere 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: Turko-Mongol and Persian cultural sphere | Statement: [Sultan Ahmad Mirza, languageSphere, Turko-Mongol and Persian cultural sphere]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageSphere
Context triple: [Sultan Ahmad Mirza, languageSphere, Turko-Mongol and Persian cultural sphere]
  • A. languageCategory
    Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
  • B. languageIndependence
    Indicates that a concept, method, or representation does not depend on any specific programming or natural language and can be applied uniformly across different languages.
  • C. languageArea chosen
    Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
  • D. languageUse
    Indicates the language or languages an entity uses for communication, expression, or interaction.
  • E. languageForm
    Indicates the specific linguistic form or expression in which something is conveyed or represented.
  • 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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded6084574819098033a9723f3e1c4 completed April 15, 2026, 12:04 a.m.
PD Predicate disambiguation batch_69de9a4a14a88190951bb8f4c60bd37b completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:11 a.m.