Triple
T37876439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwaito |
E944738
|
entity |
| Predicate | typicalBeat |
P153279
|
FINISHED |
| Object | four-on-the-floor house beat |
—
|
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: four-on-the-floor house beat | Statement: [Kwaito, typicalBeat, four-on-the-floor house beat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBeat Context triple: [Kwaito, typicalBeat, four-on-the-floor house beat]
-
A.
typicalBeatPattern
chosen
Indicates the characteristic or standard rhythmic pattern that usually occurs in a given musical or temporal context.
-
B.
typicalBeatCount
Indicates the usual or standard number of beats associated with an event, pattern, or unit (such as a musical measure or rhythmic figure).
-
C.
typicalTempoPattern
Indicates the characteristic or commonly occurring tempo progression or rhythmic pattern associated with an action or event.
-
D.
usesBeatType
Indicates that an entity employs or is based on a particular type or pattern of beat (rhythmic structure).
-
E.
usesBeatFrom
Indicates that one entity employs or incorporates the rhythmic pattern, instrumental backing, or beat originally created for or associated with another entity.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.