Triple

T32019139
Position Surface form Disambiguated ID Type / Status
Subject Shabran (historical city) E817629 entity
Predicate hasLanguageInHistory P1434 FINISHED
Object Persian 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: Persian | Statement: [Shabran (historical city), hasLanguageInHistory, Persian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLanguageInHistory
Context triple: [Shabran (historical city), hasLanguageInHistory, Persian]
  • A. hasMajorityLanguageHistorically
    Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
  • B. historicallySpokenIn chosen
    Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
  • C. hasLinguisticHeritage
    Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
  • D. historicalLanguageOfBearers
    Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
  • E. hasLinguisticLegacy
    Indicates that one entity has left a lasting influence or enduring impact on the language, linguistic practices, or linguistic development associated with another entity.
  • 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_69f348fb04e4819081f4eab040ed7959 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fe920a437081908d5174e8cf7a53a6 completed May 9, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69fe919a9a6c8190acb4483f386e6db7 completed May 9, 2026, 1:44 a.m.
Created at: May 1, 2026, 12:16 a.m.