Triple

T31802284
Position Surface form Disambiguated ID Type / Status
Subject Zubayrid regime E811772 entity
Predicate usedReligiousLegitimacy P76551 FINISHED
Object control of Mecca 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: control of Mecca | Statement: [Zubayrid regime, usedReligiousLegitimacy, control of Mecca]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedReligiousLegitimacy
Context triple: [Zubayrid regime, usedReligiousLegitimacy, control of Mecca]
  • A. religiousLegitimation
    Indicates that something is justified, authorized, or validated by reference to religious beliefs, doctrines, or institutions.
  • B. usedReligionFor chosen
    Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
  • C. isUsedByReligion
    Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
  • D. reveredByReligion
    Indicates that a religion holds a particular entity in high esteem, veneration, or sacred regard.
  • E. usesReligiousRhetoric
    Indicates that one entity employs religious language, themes, or references as part of its communication, argumentation, or persuasive efforts toward another entity or audience.
  • 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_69f348e70d188190b4637c5509f81274 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6afebd7ec8190ab696f363d84abf0 completed May 3, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69f6aca3dedc81908b519d53d2909868 completed May 3, 2026, 2:02 a.m.
Created at: April 30, 2026, 11:42 p.m.