Triple

T9549683
Position Surface form Disambiguated ID Type / Status
Subject Dhul-Kifl E230386 entity
Predicate scripturalDetailLevel P89741 FINISHED
Object briefly mentioned 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: briefly mentioned | Statement: [Dhul-Kifl, scripturalDetailLevel, briefly mentioned]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scripturalDetailLevel
Context triple: [Dhul-Kifl, scripturalDetailLevel, briefly mentioned]
  • A. scripturalExpertise
    Indicates a relationship where one entity possesses specialized knowledge or authoritative understanding of religious scriptures in relation to another entity or context.
  • B. scripturalSection
    Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
  • C. scriptureType
    Indicates the classification or category of a scripture in relation to its type or genre.
  • D. scripturalBasis
    Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
  • E. scripturalCorpus
    Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
  • F. None of above. chosen

Provenance (4 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_69ca847d3be8819099c9dad2a7e786f1 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9906bc90819086f105c453e63c83 completed April 1, 2026, 10:15 p.m.
PD Predicate disambiguation batch_69ccd58bd21881908b860e3ee469af13 completed April 1, 2026, 8:21 a.m.
PDg Predicate description generation batch_69ccd93e90048190a2b0d7c5c195ba98 completed April 1, 2026, 8:37 a.m.
Created at: March 30, 2026, 8:02 p.m.