Triple

T26381544
Position Surface form Disambiguated ID Type / Status
Subject Charles James, Duke of Rothesay E663139 entity
Predicate didNotAccedeTo P49484 FINISHED
Object throne of England 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: throne of England | Statement: [Charles James, Duke of Rothesay, didNotAccedeTo, throne of England]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: didNotAccedeTo
Context triple: [Charles James, Duke of Rothesay, didNotAccedeTo, throne of England]
  • A. didNotOverrule
    Indicates that one entity, typically a higher authority or court, chose not to overturn, reverse, or invalidate the decision or ruling made by another entity.
  • B. didNotHold
    Indicates that an expected event, condition, or relationship failed to occur or be valid.
  • C. didNotBecome chosen
    Indicates that an expected or potential change of state, role, or condition between entities did not occur.
  • D. doesNot
    Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
  • E. refusedToExplain
    Indicates that an entity declined or failed to provide an explanation about something to another entity or audience.
  • 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_69ee88374adc81909868f3bab374a32f completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f61075acf08190913f258883342993 completed May 2, 2026, 2:55 p.m.
PD Predicate disambiguation batch_69f602d2ec748190ae95154f34c7878f completed May 2, 2026, 1:57 p.m.
Created at: April 26, 2026, 11:18 p.m.