Triple
T22364258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Things to Make and Do |
E552858
|
entity |
| Predicate | hasBPMStatus |
P147373
|
FINISHED |
| Object | up-tempo |
—
|
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: up-tempo | Statement: [Things to Make and Do, hasBPMStatus, up-tempo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBPMStatus Context triple: [Things to Make and Do, hasBPMStatus, up-tempo]
-
A.
hasBPMApprox
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
-
B.
hasBroadcastStatus
Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
-
C.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
D.
hasBeat
Indicates that one entity has defeated or surpassed another in a competitive or comparative context.
-
E.
hasISRCStatus
Indicates that an entity has a specific International Standard Recording Code (ISRC) status assigned or associated with it.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d616748190921bd49039b7f6fc |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.