Triple

T30354268
Position Surface form Disambiguated ID Type / Status
Subject Huny E772101 entity
Predicate hasDynasticTransitionRole P39883 FINISHED
Object transition from Third to Fourth 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: transition from Third to Fourth Dynasty | Statement: [Huny, hasDynasticTransitionRole, transition from Third to Fourth Dynasty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDynasticTransitionRole
Context triple: [Huny, hasDynasticTransitionRole, transition from Third to Fourth Dynasty]
  • A. dynasticRole
    Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
  • B. dynasticSuccessionChangedBy
    Indicates that a change or disruption has occurred in the established line of dynastic succession due to the influence or action of the related entity.
  • C. hasDynasticSignificance
    Indicates that something holds importance or influence within the context of a dynasty’s continuity, status, or historical legacy.
  • D. dynasticStatus
    Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
  • E. dynastyChange chosen
    Indicates a transition in ruling power from one dynasty to another.
  • 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_69f2248c6f5c8190a6177842bf791a3c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6823cc2488190a733687581ca88a1 completed May 2, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69f678d019fc8190913662cd2f87b857 completed May 2, 2026, 10:21 p.m.
Created at: April 29, 2026, 7:56 p.m.