Triple

T19850762
Position Surface form Disambiguated ID Type / Status
Subject Hallelujah E476984 entity
Predicate componentRefersTo P63266 FINISHED
Object Yah as shortened form of the divine name 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: Yah as shortened form of the divine name | Statement: [Hallelujah, componentRefersTo, Yah as shortened form of the divine name]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: componentRefersTo
Context triple: [Hallelujah, componentRefersTo, Yah as shortened form of the divine name]
  • A. alsoRefersTo chosen
    Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
  • B. refersSpecificallyTo
    Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
  • C. symbolReferenced
    Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
  • D. componentRepresents
    Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
  • E. refersToPerson
    Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
  • 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_69d8e51d39d081909bcfafeaaf3d2fcc completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65867b5408190bbd12ca567c4705f completed April 20, 2026, 4:46 p.m.
PD Predicate disambiguation batch_69e537e21d2881909b1be82f02b99d40 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:51 p.m.