Triple
T32243957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redes |
E823694
|
entity |
| Predicate | hasMusicOnlySuite |
P53545
|
FINISHED |
| Object | concert suite from film score |
—
|
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: concert suite from film score | Statement: [Redes, hasMusicOnlySuite, concert suite from film score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicOnlySuite Context triple: [Redes, hasMusicOnlySuite, concert suite from film score]
-
A.
hasMusicUnit
Indicates that one entity includes, is associated with, or is organized into a specific musical unit (such as a band, ensemble, or musical subgroup).
-
B.
hasOrchestralSuite
chosen
Indicates that a musical work is associated with, or has been arranged into, an orchestral suite derived from it.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasPianoSolo
Indicates that something includes, features, or is characterized by a piano solo performance.
-
E.
hasMusicCharacteristic
Indicates that an entity possesses a specific musical feature, quality, or attribute.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 12:40 a.m.