Triple
T30898588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy... Hymns and Faith |
E787095
|
entity |
| Predicate | featuresTraditionalHymns |
P60491
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Legacy... Hymns and Faith, featuresTraditionalHymns, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTraditionalHymns Context triple: [Legacy... Hymns and Faith, featuresTraditionalHymns, yes]
-
A.
includesTraditionalSong
Indicates that one entity contains or features a traditional song as part of its content or composition.
-
B.
associatedWithHymns
chosen
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
-
C.
hymnsPreservedIn
Indicates that specific hymns have been preserved or transmitted within a particular source, collection, or medium.
-
D.
featuresTraditionalMedley
Indicates that something includes or presents a combined sequence of traditional pieces, styles, or elements performed or shown together as a medley.
-
E.
traditionallySungAfter
Indicates that one song or musical piece is customarily performed immediately following another in a cultural or traditional sequence.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a003f6083608190a5deadc7291cf70e |
completed | May 10, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_6a003c935c40819085fdb255a52ba03b |
completed | May 10, 2026, 8:06 a.m. |
Created at: April 29, 2026, 8:50 p.m.