Triple

T26583723
Position Surface form Disambiguated ID Type / Status
Subject Yıldırım Akbulut E667147 entity
Predicate servedAsSpeakerUntil P83008 FINISHED
Object 1989 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: 1989 | Statement: [Yıldırım Akbulut, servedAsSpeakerUntil, 1989]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servedAsSpeakerUntil
Context triple: [Yıldırım Akbulut, servedAsSpeakerUntil, 1989]
  • A. succeededAsSpeakerBy
    Indicates that one entity took over the role or position of speaker from another entity as their successor.
  • B. officeHeldAsSpeakerEnd chosen
    Indicates the point in time or date when an individual's tenure in the role of Speaker of a body or assembly comes to an end.
  • C. precededInOfficeAsSpeaker
    Indicates that one individual previously held the position of Speaker of an office or assembly before another individual, directly preceding them in that role.
  • D. spokeAt
    Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
  • E. lastSpeakersAssociatedWith
    Indicates a relationship where certain entities are identified as the most recent or final speakers associated with another entity, such as an event, session, or conversation.
  • 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_69ee9cfb7e548190b60a9031182f5a7e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f7979a073881909a4fde2558e6b6f3 completed May 3, 2026, 6:44 p.m.
PD Predicate disambiguation batch_69f7961550f88190b7bb8a9155458b54 completed May 3, 2026, 6:38 p.m.
Created at: April 27, 2026, 2:04 a.m.