Triple

T26672190
Position Surface form Disambiguated ID Type / Status
Subject Lord of Zeta E672362 entity
Predicate mayBeInheritedBy P106160 FINISHED
Object successor 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: successor | Statement: [Lord of Zeta, mayBeInheritedBy, successor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayBeInheritedBy
Context triple: [Lord of Zeta, mayBeInheritedBy, successor]
  • A. isInherited
    Indicates that one entity derives its characteristics, properties, or rights from another through an inheritance relationship.
  • B. losesInheritanceThrough
    Indicates that one party forfeits or is disqualified from receiving an inheritance as a consequence of another specified party or condition.
  • C. inheritedFrom
    Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
  • D. cannotBeInheritedAs
    Indicates that a property, method, or characteristic of one entity is not allowed to be passed down or inherited by another entity.
  • E. potentialFurtherInheritance chosen
    Indicates that one entity may receive additional rights, traits, or assets from another entity in the future, beyond what has already been inherited.
  • 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_69eecda00a9c8190b2691f4d89db03b6 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 27, 2026, 3:13 a.m.