Triple
T19551244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selling England by the Pound |
E489201
|
entity |
| Predicate | hasTimeSignatureComplexity |
P136553
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Selling England by the Pound, hasTimeSignatureComplexity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeSignatureComplexity Context triple: [Selling England by the Pound, hasTimeSignatureComplexity, yes]
-
A.
hasTimeSignature
Indicates that a musical work, passage, or segment is associated with a specific time signature defining its rhythmic meter.
-
B.
hasTimeSignatureChange
Indicates that the time signature changes at some point within the duration of the referenced musical segment or piece.
-
C.
hasTempoChanges
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
-
D.
hasKeySignatureDistribution
Indicates that there is a specific pattern or spread of key signatures associated with the entity, describing how frequently or prominently different key signatures occur.
-
E.
hasTempoVariety
Indicates that an entity exhibits variation or changes in tempo rather than maintaining a constant speed.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2feed48190ad49f64980dc885f |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51796b4c48190b721114dde654bd7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 1:41 p.m.