Triple

T36657872
Position Surface form Disambiguated ID Type / Status
Subject Prince Frederick Augustus, Duke of York and Albany E905041 entity
Predicate reignAsPrinceBishopEnd P192881 FINISHED
Object 1803 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: 1803 | Statement: [Prince Frederick Augustus, Duke of York and Albany, reignAsPrinceBishopEnd, 1803]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reignAsPrinceBishopEnd
Context triple: [Prince Frederick Augustus, Duke of York and Albany, reignAsPrinceBishopEnd, 1803]
  • A. reignAsPrinceBishopStart
    Indicates the time at which an individual begins serving in the role of prince-bishop.
  • B. establishedAsPrinceBishopric
    Indicates that an entity was formally created or designated as a prince-bishopric, combining both secular princely authority and ecclesiastical bishopric status.
  • C. reignAsPrinceEnd
    Indicates the point in time or event at which an individual’s tenure or role as a prince comes to an end.
  • D. hadPrinceBishop
    Indicates that an entity was governed or overseen by a prince-bishop, combining secular and ecclesiastical authority.
  • E. reignAsGrandPrinceEnd
    Indicates the time or event at which an entity’s tenure or rule as a grand prince comes to an end.
  • 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_69f76e6e3b908190970251b30f76ad71 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd2cf39b0c8190811b8a6fa9410560 completed May 8, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69fd2ad8dd988190a9899701ba00d917 completed May 8, 2026, 12:14 a.m.
PDg Predicate description generation batch_69fd2cf29f808190856ab1d43a51d5c7 completed May 8, 2026, 12:23 a.m.
Created at: May 3, 2026, 4:11 p.m.