Triple

T28298321
Position Surface form Disambiguated ID Type / Status
Subject Let the bright seraphim E713630 entity
Predicate hasSacredContext P136757 FINISHED
Object biblical narrative of Samson 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: biblical narrative of Samson | Statement: [Let the bright seraphim, hasSacredContext, biblical narrative of Samson]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSacredContext
Context triple: [Let the bright seraphim, hasSacredContext, biblical narrative of Samson]
  • A. hasSacredFunction
    Indicates that something serves a religious or holy role, purpose, or duty within a sacred context.
  • B. hasSacredNarrative chosen
    Indicates that one entity possesses, contains, or is associated with a sacred or religiously significant narrative related to another entity.
  • C. hasSacredSymbol
    Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
  • D. hasSacredPrecinct
    Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
  • E. hasSacredImage
    Indicates that one entity possesses or is associated with an image regarded as sacred or religiously significant.
  • 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_69efb524ab688190a1ce7ee7c9520932 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
Created at: April 27, 2026, 11:33 p.m.