Triple
T9422326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koiak |
E227182
|
entity |
| Predicate | traditionalHymnCollection |
P60491
|
FINISHED |
| Object | Kiahk praises |
—
|
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: Kiahk praises | Statement: [Koiak, traditionalHymnCollection, Kiahk praises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHymnCollection Context triple: [Koiak, traditionalHymnCollection, Kiahk praises]
-
A.
hymnsPreservedIn
Indicates that specific hymns have been preserved or transmitted within a particular source, collection, or medium.
-
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.
psalmCollection
Indicates that one entity is a collection or compilation that contains or groups together psalms associated with another entity.
-
D.
traditionallySungAfter
Indicates that one song or musical piece is customarily performed immediately following another in a cultural or traditional sequence.
-
E.
includesTraditionalSong
Indicates that one entity contains or features a traditional song as part of its content or composition.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2651c48190808281779fab49df |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.