Triple

T9606102
Position Surface form Disambiguated ID Type / Status
Subject Kabaka Yekka E231974 entity
Predicate usedTraditionalAuthority P18538 FINISHED
Object yes — 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: yes | Statement: [Kabaka Yekka, usedTraditionalAuthority, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedTraditionalAuthority
Context triple: [Kabaka Yekka, usedTraditionalAuthority, yes]
  • A. traditionalAuthorityOver
    Indicates that one entity holds customary or historically established power, control, or decision-making authority over another entity.
  • B. hasTraditionalRecognition
    Indicates that an entity is acknowledged or honored according to established customs, practices, or longstanding cultural traditions.
  • C. uniformAuthority
    Indicates that an authority or governing body applies rules, standards, or control consistently and uniformly across all relevant entities or situations.
  • D. usesAuthorityOf chosen
    Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
  • E. hasTraditionalInstitutions
    Indicates that an entity possesses or is associated with long-established, customary social, cultural, or governance institutions.
  • 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_69ca8485a90c819094fe40b42fde9d70 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a6006d48190adc03306533b9be6 completed April 1, 2026, 10:21 p.m.
PD Predicate disambiguation batch_69ccd5a6fd2481908efd131e207b8143 completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:08 p.m.