Triple

T9716889
Position Surface form Disambiguated ID Type / Status
Subject Rex Sacrorum E235163 entity
Predicate rankInPriestlyHierarchy P3655 FINISHED
Object highest in dignity 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: highest in dignity | Statement: [Rex Sacrorum, rankInPriestlyHierarchy, highest in dignity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankInPriestlyHierarchy
Context triple: [Rex Sacrorum, rankInPriestlyHierarchy, highest in dignity]
  • A. ecclesiasticalRank
    Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
  • B. ecclesiasticalRankRelative
    Indicates a hierarchical relationship between two ecclesiastical positions, specifying which rank is higher, lower, or otherwise ordered relative to the other within a church structure.
  • C. hasLiturgicalRank chosen
    Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
  • D. rankInPapalOrders
    Indicates the relative hierarchical position or level an entity holds within the structure of papal orders.
  • E. nobleRankInHierarchy
    Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
  • 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_69ca84cd8fa0819090a5e243ceb37003 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9e3d75e08190b4d86363595bd40d completed April 1, 2026, 10:37 p.m.
PD Predicate disambiguation batch_69cd03bfeca08190924fca43aaa9c10f completed April 1, 2026, 11:38 a.m.
Created at: March 30, 2026, 8:20 p.m.