Triple

T4758894
Position Surface form Disambiguated ID Type / Status
Subject Eumolpidae E105653 entity
Predicate sacredObligation P21134 FINISHED
Object preservation of Eleusinian rites 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: preservation of Eleusinian rites | Statement: [Eumolpidae, sacredObligation, preservation of Eleusinian rites]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sacredObligation
Context triple: [Eumolpidae, sacredObligation, preservation of Eleusinian rites]
  • A. sacredTo
    Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
  • B. sacredStatus chosen
    Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
  • C. sacramentalDiscipline
    Indicates the rules, practices, and regulations governing how religious sacraments are properly administered and received.
  • D. sacredTruce
    Indicates a formally recognized period during which hostilities or conflicts are suspended, often for religious or ceremonial reasons.
  • E. hasSpecialVowOfObedienceRegarding
    Indicates that one entity is bound by a distinct or additional vow to obey the authority, directives, or will of another specific 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_69bd43f14cac819081c7c69803648211 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd650c11f4819098cd1f490f711dc8 completed March 20, 2026, 3:17 p.m.
PD Predicate disambiguation batch_69bd6225c9488190afee5bb3619d0365 completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:20 p.m.