Triple
T13094141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maengket dance |
E310535
|
entity |
| Predicate | rhythmType |
P7864
|
FINISHED |
| Object | repetitive rhythmic patterns |
—
|
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: repetitive rhythmic patterns | Statement: [Maengket dance, rhythmType, repetitive rhythmic patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rhythmType Context triple: [Maengket dance, rhythmType, repetitive rhythmic patterns]
-
A.
hasRhythmicStyle
chosen
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
B.
rhythmicOrganization
Indicates how temporal patterns, accents, and durations are structured or arranged in relation to one another within a sequence or system.
-
C.
regimeType
Indicates the form or system of governance under which an entity (such as a state or organization) is ruled or administered.
-
D.
ritualDrumType
Indicates the specific type or category of drum used in a ritual or ceremonial context.
-
E.
hasRhythmicOrigin
Indicates that something originates from, is derived from, or is fundamentally based on rhythm or rhythmic patterns.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.