Triple
T12843824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eritrean Orthodox liturgy |
E307120
|
entity |
| Predicate | hasMusicalHeritage |
P42607
|
FINISHED |
| Object | Saint Yared's hymns |
—
|
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: Saint Yared's hymns | Statement: [Eritrean Orthodox liturgy, hasMusicalHeritage, Saint Yared's hymns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalHeritage Context triple: [Eritrean Orthodox liturgy, hasMusicalHeritage, Saint Yared's hymns]
-
A.
hasCulturalLegacyIn
chosen
Indicates that an entity has left a lasting cultural influence, impact, or heritage within a particular place, community, or cultural context.
-
B.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
C.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
D.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
E.
hasRhythmOrigin
Indicates that one rhythm, style, or rhythmic pattern originates from, is derived from, or has its roots in another source.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.