Triple

T14573891
Position Surface form Disambiguated ID Type / Status
Subject Prince Charles of Belgium E341987 entity
Predicate endTime (as Prince Regent of Belgium) P2721 FINISHED
Object 1950-07-20 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: 1950-07-20 | Statement: [Prince Charles of Belgium, endTime (as Prince Regent of Belgium), 1950-07-20]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endTime (as Prince Regent of Belgium)
Context triple: [Prince Charles of Belgium, endTime (as Prince Regent of Belgium), 1950-07-20]
  • A. successorAsGrandDukeOfLuxembourg
    Indicates that one person became the next Grand Duke of Luxembourg following another person in that role.
  • B. endOfReign chosen
    Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
  • C. reignAsKingOfBurgundyEnd
    Indicates the time or event at which an individual's reign as king of Burgundy comes to an end.
  • D. reignEndAsDukeOfAustria
    Indicates the time or event at which an individual’s rule in the role of Duke of Austria comes to an end.
  • E. predecessorAsGrandDukeOfLuxembourg
    Indicates that one entity previously held the position of Grand Duke of Luxembourg immediately before the other entity.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f49d58819094fcd2a702e146cb completed April 14, 2026, 9:39 p.m.
PD Predicate disambiguation batch_69de656a953481909a4645b004c40de7 completed April 14, 2026, 4:03 p.m.
Created at: April 10, 2026, 1:24 a.m.