Triple

T11011758
Position Surface form Disambiguated ID Type / Status
Subject Mutasarrifate of Jerusalem E260263 entity
Predicate reasonForSpecialStatus P30133 FINISHED
Object religious importance 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: religious importance | Statement: [Mutasarrifate of Jerusalem, reasonForSpecialStatus, religious importance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForSpecialStatus
Context triple: [Mutasarrifate of Jerusalem, reasonForSpecialStatus, religious importance]
  • A. reasonForSpecialMeasures
    Indicates that one entity specifies the justification or cause for which special measures or exceptional actions are taken regarding another entity.
  • B. statedReason
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • C. reasonForGrant
    Indicates the justification, purpose, or cause for which a grant is awarded or provided.
  • D. reasonForStatus chosen
    Indicates the explanation or cause underlying a particular state or condition.
  • E. reasonForDisqualification
    Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
  • 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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7978a57a881909b4ceae0ebe21b78 completed April 9, 2026, 12:11 p.m.
PD Predicate disambiguation batch_69d72e96be6c8190a46c69f61b2d8cd4 completed April 9, 2026, 4:44 a.m.
Created at: April 8, 2026, 9:25 p.m.