Triple
T5388588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Crack Commandments |
E120264
|
entity |
| Predicate | tempoCategory |
P38111
|
FINISHED |
| Object | mid-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: mid-tempo | Statement: [Ten Crack Commandments, tempoCategory, mid-tempo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoCategory Context triple: [Ten Crack Commandments, tempoCategory, mid-tempo]
-
A.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
B.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
-
C.
durationCategory
Indicates the classification of an event or state based on how long it lasts, grouping it into a specific duration range or type.
-
D.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
tempoFeature
chosen
Indicates a relationship where a musical or rhythmic element is characterized by, or associated with, a specific tempo-related property or feature.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd871573b48190aa60871be56847ae |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.