Triple

T34209943
Position Surface form Disambiguated ID Type / Status
Subject Elagabal E877625 entity
Predicate priesthoodHeldBy P52821 FINISHED
Object family of the Emesene dynasty 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: family of the Emesene dynasty | Statement: [Elagabal, priesthoodHeldBy, family of the Emesene dynasty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: priesthoodHeldBy
Context triple: [Elagabal, priesthoodHeldBy, family of the Emesene dynasty]
  • A. priesthoodDescribedBy
    Indicates that a priesthood is documented, characterized, or explained by a particular description or source.
  • B. priestlyDivision
    Indicates a relationship where an individual is assigned to or associated with a specific priestly division or order within a religious hierarchy.
  • C. ecclesiasticalRole
    Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
  • D. hadPriesthood chosen
    Indicates that an entity possessed or held a recognized priestly office or religious authority.
  • E. ordainedIn
    Indicates that an individual was formally appointed or consecrated to a religious office or role at a specific place or within a particular institution.
  • 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_69f349b0b4bc819088c1552424089ee9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71054384481908897507876233248 completed May 3, 2026, 9:07 a.m.
PD Predicate disambiguation batch_69f70f3c5bfc81908585f52e196dafe5 completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 1:55 a.m.