Triple

T5909007
Position Surface form Disambiguated ID Type / Status
Subject Shir Shel Yom E131413 entity
Predicate hasComponentPsalm P66876 FINISHED
Object Psalm 81 E148105 NE 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: Psalm 81 | Statement: [Shir Shel Yom, hasComponentPsalm, Psalm 81]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Psalm 81
Context triple: [Shir Shel Yom, hasComponentPsalm, Psalm 81]
  • A. Psalm 81 chosen
    Psalm 81 is a biblical song of praise and admonition that calls Israel to celebrate God’s deliverance while warning them to remain faithful to His covenant.
  • B. Psalm 95
    Psalm 95 is a biblical hymn traditionally used in Jewish and Christian worship that calls on the faithful to joyfully praise God and heed His voice.
  • C. Psalm 80
    Psalm 80 is a biblical lament psalm pleading for God’s restoration and favor upon Israel, traditionally associated with the psalmist Asaph.
  • D. Psalm 135
    Psalm 135 is a biblical hymn found in the Old Testament that praises God’s sovereignty and mighty acts on behalf of Israel, often used in Jewish and Christian liturgy.
  • E. Psalm 78
    Psalm 78 is a lengthy historical psalm in the Hebrew Bible that recounts Israel’s past failures and God’s enduring faithfulness as a warning and instruction to future generations.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c008593a44819081a07ae0efe6c574 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c049fdb3e08190a72337ab4f48bc8e completed March 22, 2026, 7:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b16f568081908839cd2403b7534c completed March 23, 2026, 3:20 a.m.
Created at: March 22, 2026, 3:59 p.m.