Triple

T1247870
Position Surface form Disambiguated ID Type / Status
Subject Taliban E26807 entity
Predicate interpretationOfSharia P5494 FINISHED
Object strict 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: strict | Statement: [Taliban, interpretationOfSharia, strict]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: interpretationOfSharia
Context triple: [Taliban, interpretationOfSharia, strict]
  • A. religiousJurisdiction
    Indicates that one entity holds official religious authority or governance over another entity or area.
  • B. normativeStatusInIslam
    Indicates the evaluative ruling or status that Islamic law or ethics assigns to an action, practice, or state (e.g., obligatory, recommended, permissible, disliked, or forbidden).
  • C. classifiesMuslimsWhoDiffer
    Indicates treating or labeling Muslims who hold differing beliefs, practices, or views as a distinct or separate group.
  • D. viewsHalakhaAs
    Indicates that one entity regards or interprets Halakha (Jewish law) in a particular way, such as considering it authoritative, binding, flexible, or symbolic.
  • E. theologicalInterpretation chosen
    Indicates a relationship where an event, text, or phenomenon is understood or explained through religious or doctrinal beliefs and principles.
  • 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_69a49487a9c48190ba9b05348fd1b53f completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf827e088190a16d845cea14f2c9 completed March 1, 2026, 10:36 p.m.
PD Predicate disambiguation batch_69a4bb6b075881908e867c25b5080e25 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:47 p.m.