Triple
T24079015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | March of the Pigs |
E596454
|
entity |
| Predicate | featuresTimeSignature |
P1367
|
FINISHED |
| Object | 7/8 |
—
|
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: 7/8 | Statement: [March of the Pigs, featuresTimeSignature, 7/8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTimeSignature Context triple: [March of the Pigs, featuresTimeSignature, 7/8]
-
A.
hasTimeSignature
chosen
Indicates that a musical work, passage, or segment is associated with a specific time signature defining its rhythmic meter.
-
B.
hasTimeSignatureComplexity
Indicates that one musical work, passage, or pattern is characterized by a specified level or type of complexity in its time signature.
-
C.
timeSignatureChange
Indicates a change from one musical time signature to another within a piece or passage.
-
D.
tempoFeature
Indicates a relationship where a musical or rhythmic element is characterized by, or associated with, a specific tempo-related property or feature.
-
E.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db20ca648190bb168808623119da |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:43 p.m.