Triple

T10769846
Position Surface form Disambiguated ID Type / Status
Subject Upangas E254044 entity
Predicate scripturalLevel P2326 FINISHED
Object secondaryToPrimaryAgamas 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: secondaryToPrimaryAgamas | Statement: [Upangas, scripturalLevel, secondaryToPrimaryAgamas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scripturalLevel
Context triple: [Upangas, scripturalLevel, secondaryToPrimaryAgamas]
  • A. scripturalDetailLevel
    Indicates the degree of specificity or granularity with which scriptural content is presented, referenced, or analyzed in a given context.
  • B. scripturalExpertise
    Indicates a relationship where one entity possesses specialized knowledge or authoritative understanding of religious scriptures in relation to another entity or context.
  • C. scripturalBasis chosen
    Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
  • D. scripturalReference
    Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
  • E. scripturalUse
    Indicates that one entity is used as a scriptural reference, source, or basis within the context or content of another entity.
  • 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_69d6aa5f54f4819082d0bbcb6f8797e6 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d732307fb88190ba1447f68523c58a completed April 9, 2026, 4:59 a.m.
PD Predicate disambiguation batch_69d6f31455648190b5c24690487b1b54 completed April 9, 2026, 12:30 a.m.
Created at: April 8, 2026, 9:16 p.m.