Triple

T6036554
Position Surface form Disambiguated ID Type / Status
Subject Napoleon I (as heir) E134435 entity
Predicate hasDynasticPrinciple P31298 FINISHED
Object hereditary monarchy 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: hereditary monarchy | Statement: [Napoleon I (as heir), hasDynasticPrinciple, hereditary monarchy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDynasticPrinciple
Context triple: [Napoleon I (as heir), hasDynasticPrinciple, hereditary monarchy]
  • A. dynasticPrinciple chosen
    Indicates that a relationship is governed by rules of hereditary succession or dynastic inheritance within a ruling family or lineage.
  • B. dynasticInheritance
    Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
  • C. hasDynasticOrder
    Indicates that there exists a specific sequence or hierarchy of dynasties or ruling lines associated with the subject.
  • D. isDynastic
    Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
  • E. dynasticStatus
    Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
  • 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_69c00875db5c819099dd5bb833ec43c2 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c056cb06508190a90beb4d9d083835 completed March 22, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69c049e9a68c81909da0cfe4779ce9b5 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:08 p.m.