Triple

T35032261
Position Surface form Disambiguated ID Type / Status
Subject megas doux E1010811 entity
Predicate successorOfficeInOtherStates P201592 FINISHED
Object grand admiral in successor states 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: grand admiral in successor states | Statement: [megas doux, successorOfficeInOtherStates, grand admiral in successor states]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorOfficeInOtherStates
Context triple: [megas doux, successorOfficeInOtherStates, grand admiral in successor states]
  • A. successorOfficeTo
    Indicates that one office or position directly follows and replaces another in an official sequence or hierarchy.
  • B. successorOfficeEstablished
    Indicates that a new office or position was formally created to replace or succeed a previous one.
  • C. successorOfficeHolder
    Indicates that one office holder directly follows another in occupying the same official position.
  • D. declaresSuccessorOffice
    Indicates that an entity formally designates another entity to assume a particular office or position as its successor.
  • E. successorProvinceOrState
    Indicates that one province or state has officially replaced or continued the role of another as its successor.
  • 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_69f76dcea02c81908542a223f6d5059f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a000a1d8fa88190a1d82ac746565c48 completed May 10, 2026, 4:31 a.m.
PD Predicate disambiguation batch_6a0008b26eb88190ae03b2309a614774 completed May 10, 2026, 4:25 a.m.
PDg Predicate description generation batch_6a000a1c8f8881908293ab4f7207d25f completed May 10, 2026, 4:31 a.m.
Created at: May 3, 2026, 4:01 p.m.