Triple
T31189491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallelujah psalm |
E795142
|
entity |
| Predicate | typicalEnding |
—
|
GENERATED |
| Object | “Hallelujah” |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnding Context triple: [Hallelujah psalm, typicalEnding, “Hallelujah”]
-
A.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
-
B.
typicalClosing
Indicates that an entity represents a standard or commonly used way of ending or concluding another entity (such as a message, document, or interaction).
-
C.
typicalEndRelation
chosen
Indicates that one event, state, or process is the usual or characteristic endpoint or outcome of another.
-
D.
alternateEnding
Indicates that one version of a work provides a different conclusion or final sequence of events compared to the original or primary ending.
-
E.
notableEnding
Indicates that an entity concludes or finishes in a way that is remarkable, memorable, or otherwise noteworthy.
- F. None of above.
Provenance (1 batch)
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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:08 p.m.