Triple

T5508574
Position Surface form Disambiguated ID Type / Status
Subject Psalm 79 E144504 entity
Predicate possibleHistoricalContext P1409 FINISHED
Object Babylonian destruction of Jerusalem in 586 BCE 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: Babylonian destruction of Jerusalem in 586 BCE | Statement: [Psalm 79, possibleHistoricalContext, Babylonian destruction of Jerusalem in 586 BCE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleHistoricalContext
Context triple: [Psalm 79, possibleHistoricalContext, Babylonian destruction of Jerusalem in 586 BCE]
  • A. hasHistoricalContext chosen
    Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
  • B. historicalBackground
    Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
  • C. historicalReference
    Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
  • D. historicalReason
    Indicates that one entity exists, occurs, or is justified because of causes, events, or circumstances rooted in the past of another entity.
  • E. historicallyConsidered
    Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
  • 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_69c008f6b5048190a09064116062cf69 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f4a80d88190bab0056c4c78be93 completed March 22, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69c01b07bde08190b3933b96bdc70dd5 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:33 p.m.