Triple

T8653068
Position Surface form Disambiguated ID Type / Status
Subject Queen of England E205145 entity
Predicate hasDynasticFunction P84146 FINISHED
Object securing succession 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: securing succession | Statement: [Queen of England, hasDynasticFunction, securing succession]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDynasticFunction
Context triple: [Queen of England, hasDynasticFunction, securing succession]
  • A. isDynastic
    Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
  • B. hasDynasticOrder
    Indicates that there exists a specific sequence or hierarchy of dynasties or ruling lines associated with the subject.
  • C. dynasticStatus
    Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
  • D. dynasticLegacy
    Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
  • E. dynasticType
    Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
  • F. None of above. chosen

Provenance (4 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_69ca834e56848190abb0eeaec9dedd32 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc484206d881908017897dada63124 completed March 31, 2026, 10:18 p.m.
PD Predicate disambiguation batch_69cc45619460819091e83ffdec99c865 completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc473e44988190a3b02498e5fff668 completed March 31, 2026, 10:14 p.m.
Created at: March 30, 2026, 6:29 p.m.