Triple
T36906398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finlandia |
E912788
|
entity |
| Predicate | usedForHymnText |
P60491
|
FINISHED |
| Object | Be Still, My Soul |
—
|
NE NERFINISHED |
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: Be Still, My Soul | Statement: [Finlandia, usedForHymnText, Be Still, My Soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForHymnText Context triple: [Finlandia, usedForHymnText, Be Still, My Soul]
-
A.
usedAsStandardGospelTextIn
Indicates that a text served as the primary or authoritative gospel text within a specified context, such as a community, tradition, or time period.
-
B.
hymnTuneName
Indicates the specific musical tune or melody name associated with a hymn.
-
C.
associatedWithHymns
chosen
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
-
D.
hymnsPreservedIn
Indicates that specific hymns have been preserved or transmitted within a particular source, collection, or medium.
-
E.
usedAsChant
Indicates that something (typically a phrase, text, or sound) is employed as a chant in a ritual, performance, or repetitive vocal practice.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:13 p.m.