Triple
T29536766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shamanic Drum |
E749366
|
entity |
| Predicate | primaryRhythmType |
P203215
|
FINISHED |
| Object | steady pulse |
—
|
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: steady pulse | Statement: [The Shamanic Drum, primaryRhythmType, steady pulse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRhythmType Context triple: [The Shamanic Drum, primaryRhythmType, steady pulse]
-
A.
primaryRhythmSource
Indicates that one entity serves as the main provider or origin of the rhythmic pattern for another entity.
-
B.
primarySin
Indicates a fundamental or chief moral wrongdoing attributed to an entity, often viewed as the root or most significant sin in a given context.
-
C.
hasRhythmicOrigin
Indicates that something originates from, is derived from, or is fundamentally based on rhythm or rhythmic patterns.
-
D.
primaryRaceType
Indicates the main or predominant race category associated with an entity, as opposed to any secondary or additional race classifications.
-
E.
typeOfPrimacy
Indicates that one entity holds a primary, leading, or most important status or precedence over others in a given 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_6a013d70e2448190a034e8a11a457008 |
completed | May 11, 2026, 2:22 a.m. |
Created at: April 28, 2026, 4:59 p.m.