Triple

T30851721
Position Surface form Disambiguated ID Type / Status
Subject Yazidi temples E785797 entity
Predicate entryPractice P38187 FINISHED
Object removal of shoes before entering sacred areas 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: removal of shoes before entering sacred areas | Statement: [Yazidi temples, entryPractice, removal of shoes before entering sacred areas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: entryPractice
Context triple: [Yazidi temples, entryPractice, removal of shoes before entering sacred areas]
  • A. entryMode
    Indicates the manner or method by which something is entered, recorded, or input into a system or context.
  • B. entryFor
    Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
  • C. entryCondition chosen
    Indicates the prerequisite state, criteria, or circumstances that must be satisfied before entering or initiating a particular process, state, or context.
  • D. entryControl
    Indicates a relationship where one entity regulates or authorizes another entity’s access to a place, system, or resource.
  • E. enteredInto
    Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another 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_69f224b850848190a4af4ccf8ddadcdf completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6917c8d8c8190b4091f3ef57834bb completed May 3, 2026, 12:06 a.m.
PD Predicate disambiguation batch_69f68b7d2794819092fef8a63f4f3de8 completed May 2, 2026, 11:40 p.m.
Created at: April 29, 2026, 8:46 p.m.