Triple

T30472526
Position Surface form Disambiguated ID Type / Status
Subject Quintuplex Psalterium E775342 entity
Predicate hasScripturalSection P5605 FINISHED
Object Old Testament NE NERFINISHED

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: Old Testament | Statement: [Quintuplex Psalterium, hasScripturalSection, Old Testament]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasScripturalSection
Context triple: [Quintuplex Psalterium, hasScripturalSection, Old Testament]
  • A. hasScripture chosen
    Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
  • B. scripturalSection
    Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
  • C. hasViewOnScripture
    Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
  • D. hasSect
    Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
  • E. hasVersesIn
    Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
  • 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_69f22497341481909c21ba329fadaa6b completed April 29, 2026, 3:32 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 29, 2026, 8:11 p.m.