Triple

T22340261
Position Surface form Disambiguated ID Type / Status
Subject Gurudwara Data Bandi Chhod E552252 entity
Predicate languageOfScriptureRecited P1187 FINISHED
Object Gurmukhi 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: Gurmukhi | Statement: [Gurudwara Data Bandi Chhod, languageOfScriptureRecited, Gurmukhi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageOfScriptureRecited
Context triple: [Gurudwara Data Bandi Chhod, languageOfScriptureRecited, Gurmukhi]
  • A. hasLanguageOfScripture chosen
    Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
  • B. usedScriptureTranslation
    Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
  • C. languageOfScripturalTradition
    Indicates the language in which a given scriptural or religious textual tradition is expressed or transmitted.
  • D. recognizesScripturesFrom
    Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
  • E. typicalLanguageOfReadings
    Indicates the language that is most commonly used for readings or interpretations associated with a given 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_69e11e494eec81909c4d2d51f69499d9 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15783637c8190b77885f4e23d7ee5 completed April 29, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69e7300c20088190a59e5bf9e70384f3 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:43 p.m.