Triple

T1237726
Position Surface form Disambiguated ID Type / Status
Subject Psalm 151 E26583 entity
Predicate structureInHebrewWitness P17710 FINISHED
Object composite of two shorter Hebrew psalms 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: composite of two shorter Hebrew psalms | Statement: [Psalm 151, structureInHebrewWitness, composite of two shorter Hebrew psalms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: structureInHebrewWitness
Context triple: [Psalm 151, structureInHebrewWitness, composite of two shorter Hebrew psalms]
  • A. positionInHebrewBible
    Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
  • B. subsectionOfTanakh
    Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
  • C. positionInTanakh
    Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
  • D. viaStructure
    Indicates that one entity is connected to or accessed through a particular structural element or medium.
  • E. segmentStructure chosen
    Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure 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_69a4948571c88190a9191e451e6035fd completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf3f07c08190a402e8341c1f38cc completed March 1, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69a4bb67d52c8190815d6356b79d6ed5 completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:47 p.m.