Triple
T33609381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C4 |
E860947
|
entity |
| Predicate | containsReusedBeats |
P201916
|
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: [C4, containsReusedBeats, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsReusedBeats Context triple: [C4, containsReusedBeats, yes]
-
A.
usesBeatFrom
Indicates that one entity employs or incorporates the rhythmic pattern, instrumental backing, or beat originally created for or associated with another entity.
-
B.
usesBeatType
Indicates that an entity employs or is based on a particular type or pattern of beat (rhythmic structure).
-
C.
hasBeatCount
Indicates that one entity specifies or is associated with the number of beats (e.g., rhythmic units or pulses) of another entity.
-
D.
melodyReusedBy
Indicates that a melody originally used in one work is later reused or incorporated in another work.
-
E.
hasBeat
Indicates that one entity has defeated or surpassed another in a competitive or comparative context.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_6a0031ec758c81908a3877bc19ce2701 |
completed | May 10, 2026, 7:21 a.m. |
Created at: May 1, 2026, 1:41 a.m.