Triple

T5275179
Position Surface form Disambiguated ID Type / Status
Subject Parmalim E119355 entity
Predicate religiousTextType P61691 FINISHED
Object oral tradition 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: oral tradition | Statement: [Parmalim, religiousTextType, oral tradition]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousTextType
Context triple: [Parmalim, religiousTextType, oral tradition]
  • A. religiousTextOf
    Indicates that one entity is a religious text that is sacred to, foundational for, or primarily associated with another entity (such as a religion, denomination, or faith community).
  • B. religiousTextTradition
    Indicates that a religious text is associated with, originates from, or is authoritative within a particular religious tradition or denomination.
  • C. religiousElement
    Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
  • D. religiousTextRole
    Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
  • E. religiousTextLanguageOf
    Indicates that a particular language is the language in which a given religious text is written or primarily expressed.
  • 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_69bd446c38e081908cdaf113bdf86790 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7c23bed88190b406dee21957d823 completed March 20, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69bd77c83d1c8190bd8b9616113d413c completed March 20, 2026, 4:37 p.m.
PDg Predicate description generation batch_69bd782108bc8190be68ccce09cfd3ef completed March 20, 2026, 4:38 p.m.
Created at: March 20, 2026, 1:51 p.m.