Triple

T26704928
Position Surface form Disambiguated ID Type / Status
Subject Shona traditional religion E673262 entity
Predicate vadzimuDefinedAs P161138 FINISHED
Object ancestral spirits 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: ancestral spirits | Statement: [Shona traditional religion, vadzimuDefinedAs, ancestral spirits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vadzimuDefinedAs
Context triple: [Shona traditional religion, vadzimuDefinedAs, ancestral spirits]
  • A. vadi
    Indicates that one entity is speaking, arguing, or verbally expressing something to another entity.
  • B. hasVadi
    Indicates that one musical element (such as a note or pitch) serves as the primary or most prominent tone (vadi) in relation to a specific raga or melodic framework.
  • C. vakul
    Indicates a relationship or action between entities, but the specific meaning of the predicate "vakul" is unclear without additional context or definition.
  • D. valueDefinedBy
    Indicates that the value of one entity is determined, specified, or constrained by another entity.
  • E. vise
    Indicates that one entity firmly grips, clamps, or holds another in place, typically restricting its movement or separating it from other objects.
  • 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_69eecda2b49c8190a6c481cfc4c07954 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f617b8e61881909eef2e8eaf1bc969 completed May 2, 2026, 3:26 p.m.
PD Predicate disambiguation batch_69f60b8dfa0c8190864e1a940024d0a0 completed May 2, 2026, 2:34 p.m.
PDg Predicate description generation batch_69f6106d346c8190868489f36c65b6ec completed May 2, 2026, 2:55 p.m.
Created at: April 27, 2026, 3:33 a.m.