Triple

T33827317
Position Surface form Disambiguated ID Type / Status
Subject SS Empress of Britain (2000) E866990 entity
Predicate hasSuccessorNames P200068 FINISHED
Object multiple later names under different operators 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 later names under different operators | Statement: [SS Empress of Britain (2000), hasSuccessorNames, multiple later names under different operators]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuccessorNames
Context triple: [SS Empress of Britain (2000), hasSuccessorNames, multiple later names under different operators]
  • A. hasSuccessors
    Indicates that an entity is followed or replaced by one or more subsequent entities in a sequence, process, or lineage.
  • B. hasSuccessorBodyName
    Indicates that one body is immediately followed or replaced by another body, identifying the name of its successor in a sequence or lineage.
  • C. 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.
  • D. hasSuccessorMembers
    Indicates that one set of members follows or replaces another set of members in a sequence, order, or organizational structure.
  • E. hasSuccessorNameConflict
    Indicates that an entity’s successor has a name that conflicts (e.g., duplicates or clashes) with another existing or expected name in the system.
  • 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_69f34991dd248190a659541588506b3c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff6fba1a5c8190a660279a6271d785 completed May 9, 2026, 5:32 p.m.
PD Predicate disambiguation batch_69ff6f59388c8190a7d6ab7bc7705bc0 completed May 9, 2026, 5:31 p.m.
PDg Predicate description generation batch_69ff6fb9691c819082ee2f3c648b7dc1 completed May 9, 2026, 5:32 p.m.
Created at: May 1, 2026, 1:46 a.m.