Triple

T21926081
Position Surface form Disambiguated ID Type / Status
Subject A∴A∴ E541446 entity
Predicate hasSuccessorGroups P81788 FINISHED
Object multiple lineages claiming continuity 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: multiple lineages claiming continuity | Statement: [A∴A∴, hasSuccessorGroups, multiple lineages claiming continuity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuccessorGroups
Context triple: [A∴A∴, hasSuccessorGroups, multiple lineages claiming continuity]
  • A. hasSuccessorMembers
    Indicates that one set of members follows or replaces another set of members in a sequence, order, or organizational structure.
  • B. hasSuccessorUsers
    Indicates that one user or set of users is followed or replaced by another user or set of users in a sequence or succession.
  • C. successorGroups chosen
    Indicates that one group is the direct successor or follow-up group to another group in some sequence or lineage.
  • D. hasFlagshipSuccessor
    Indicates that one entity serves as the primary or leading successor to another, typically replacing it as the main or flagship version, product, or instance.
  • E. haveSubgroups
    Indicates that an entity is organized into smaller constituent groups that are part of it.
  • 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_69e0c47d74488190a15119108794a307 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f123fb6af08190b3562f547d4d2895 completed April 28, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69e6f5efc208819091ed2cf6841fa600 completed April 21, 2026, 3:58 a.m.
Created at: April 16, 2026, 7:46 p.m.