Triple
T4466074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Montserrat |
E98379
|
entity |
| Predicate | musicalSymbol |
P56669
|
FINISHED |
| Object | harp |
—
|
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: harp | Statement: [Coat of arms of Montserrat, musicalSymbol, harp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalSymbol Context triple: [Coat of arms of Montserrat, musicalSymbol, harp]
-
A.
musicalAttribute
Indicates a relationship where a musical work, performance, or element is characterized by a specific musical property or quality (such as tempo, key, style, or mood).
-
B.
musicalFunction
Indicates the specific role or function an entity plays within a musical context, such as its harmonic, structural, or performative purpose in a piece or performance.
-
C.
musicElement
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
-
D.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
E.
musicalMode
Indicates the specific tonal framework or scale system (mode) in which a piece of music or musical passage is organized.
- F. None of above. chosen
Provenance (4 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
| PDg | Predicate description generation | batch_69b356f9afc48190acb50c45a310e072 |
completed | March 13, 2026, 12:14 a.m. |
Created at: March 12, 2026, 11:34 p.m.