Triple

T531173
Position Surface form Disambiguated ID Type / Status
Subject Prince-electors of the Holy Roman Empire E12224 entity
Predicate hadRank P4202 FINISHED
Object highest princes of the Empire 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 princes of the Empire | Statement: [Prince-electors of the Holy Roman Empire, hadRank, highest princes of the Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadRank
Context triple: [Prince-electors of the Holy Roman Empire, hadRank, highest princes of the Empire]
  • A. hasRankCategory
    Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
  • B. rankedBy
    Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
  • C. highestRankIn chosen
    Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
  • D. usesRank
    Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
  • E. hasRankingCategory
    Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
  • 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_69a4933208e88190891f5debab1b776d completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985e51908190a34aa82ea9dbee1e completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b257108190a537dffbb9d621b5 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.