Triple

T897013
Position Surface form Disambiguated ID Type / Status
Subject Eleusinian Mysteries E19366 entity
Predicate requiredCondition P100 FINISHED
Object no ritual pollution such as homicide 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: no ritual pollution such as homicide | Statement: [Eleusinian Mysteries, requiredCondition, no ritual pollution such as homicide]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiredCondition
Context triple: [Eleusinian Mysteries, requiredCondition, no ritual pollution such as homicide]
  • A. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • B. obligationCondition
    Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
  • C. requires chosen
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • D. authorizationCondition
    Indicates the specific rules or requirements that must be satisfied for an action or access to be legally or formally authorized.
  • E. hasCondition
    Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad2550c88190a624eb5627d472ad completed March 1, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69a4aa9635608190a297e2067b8dcee2 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.