Triple

T36243844
Position Surface form Disambiguated ID Type / Status
Subject Greater Court Hymns E891599 entity
Predicate religiousOrCulticRole P51786 FINISHED
Object ancestral worship 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: ancestral worship | Statement: [Greater Court Hymns, religiousOrCulticRole, ancestral worship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousOrCulticRole
Context triple: [Greater Court Hymns, religiousOrCulticRole, ancestral worship]
  • A. religiousAndSpiritualRole
    Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
  • B. religiousOrientationRole
    Indicates a role or position that an entity holds in relation to a particular religious orientation or affiliation.
  • C. regionReligiousRole
    Indicates the role or function that religion plays within a particular region, such as its religious status, significance, or designated religious purpose.
  • D. religiousTextRole
    Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
  • E. associatedReligionRole chosen
    Indicates that one entity holds a specific religious role, office, or function in relation to 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_69f76e44993481908fa75e4c48d0aab3 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ffe12ee59c8190bc7da386e6d5332d completed May 10, 2026, 1:36 a.m.
PD Predicate disambiguation batch_69ffe0a138bc8190a3d4b48cd579e985 completed May 10, 2026, 1:34 a.m.
Created at: May 3, 2026, 4:09 p.m.