Triple
T33682374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sacred Harp |
E862935
|
entity |
| Predicate | musicNotationSystem |
P4882
|
FINISHED |
| Object | shape-note notation |
—
|
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: shape-note notation | Statement: [The Sacred Harp, musicNotationSystem, shape-note notation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicNotationSystem Context triple: [The Sacred Harp, musicNotationSystem, shape-note notation]
-
A.
musicScoreType
Indicates the specific type or category of a musical score associated with a piece of music.
-
B.
musicalSymbol
Indicates that one entity is a musical notation mark or sign associated with another entity in a musical context.
-
C.
typicalNotation
chosen
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
D.
formalNotation
Indicates that one entity is the formal symbolic or notational representation of another entity or concept.
-
E.
musicScoreBy
Indicates that a musical score was created or composed by a particular agent or entity.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:43 a.m.