Triple
T11594838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tragic Overture, Op. 81 |
E274973
|
entity |
| Predicate | isAbstractMusic |
P100502
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tragic Overture, Op. 81, isAbstractMusic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAbstractMusic Context triple: [Tragic Overture, Op. 81, isAbstractMusic, true]
-
A.
isMusicalWork
Indicates that one entity is a musical composition or piece created as an artistic work.
-
B.
isInstrumental
Indicates that one entity serves as the means, tool, or instrument by which another entity performs an action or achieves an outcome.
-
C.
isRecordedMusic
Indicates that something is music that has been captured and stored in a recorded form, rather than being performed live in the moment.
-
D.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
E.
musicalBasisFor
Indicates that one musical work, idea, or element serves as the foundational source or inspiration upon which another musical work, idea, or element is built or derived.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.