Triple

T4151727
Position Surface form Disambiguated ID Type / Status
Subject Vulko Chervenkov E89920 entity
Predicate officeEndTime (Prime Minister of Bulgaria) P371 FINISHED
Object 1956-04-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: 1956-04-20 | Statement: [Vulko Chervenkov, officeEndTime (Prime Minister of Bulgaria), 1956-04-20]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: officeEndTime (Prime Minister of Bulgaria)
Context triple: [Vulko Chervenkov, officeEndTime (Prime Minister of Bulgaria), 1956-04-20]
  • A. officeEndTime (Governor of Kursk Oblast)
    Indicates the time at which the Governor of Kursk Oblast’s term in office concludes.
  • B. officeStartTime (Vice President of Russia)
    Indicates the time at which the Vice President of Russia officially began their term in office.
  • C. officeStartTime (Governor of Kursk Oblast)
    Indicates the time at which the Governor of Kursk Oblast officially begins their term in office.
  • D. endTimeAsDeputyPrimeMinister
    Indicates the date and time at which an individual’s tenure in the role of Deputy Prime Minister comes to an end.
  • E. primeMinisterTermEnd chosen
    Indicates the date or point in time when a person's tenure as prime minister comes to an end.
  • 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_69aed95a59a881909b26e70b42c6811a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af033ef6648190adde17f943d89c78 completed March 9, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69af018c101081909070da5b11e5eb3d completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:44 p.m.