Triple
T430790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastertide |
E9706
|
entity |
| Predicate | musicFeature |
P9125
|
FINISHED |
| Object | frequent singing of the Alleluia |
—
|
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: frequent singing of the Alleluia | Statement: [Eastertide, musicFeature, frequent singing of the Alleluia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicFeature Context triple: [Eastertide, musicFeature, frequent singing of the Alleluia]
-
A.
notableSongCharacteristic
chosen
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
B.
musicKey
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
C.
musicVideoFeatures
Indicates that a music video includes or prominently showcases a particular person, group, or element.
-
D.
genreFeatures
Indicates that a particular genre is characterized or defined by certain features or attributes.
-
E.
musicDriven
Indicates that one entity’s behavior, structure, or progression is guided, influenced, or determined primarily by music or musical elements.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeef065c81908ed30528a61da132 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.