Triple
T23812160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoga |
E589884
|
entity |
| Predicate | hasDanceableBeat |
P91533
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yoga, hasDanceableBeat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDanceableBeat Context triple: [Yoga, hasDanceableBeat, true]
-
A.
hasDanceableRhythm
chosen
Indicates that something possesses a rhythm or beat suitable for dancing.
-
B.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
-
C.
hasDanceQuality
Indicates that something possesses a particular characteristic or attribute related to dance, such as style, skill, or expressive quality.
-
D.
hasBPMApprox
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
-
E.
hasDanceDiscoVersion
Indicates that one entity has a disco-style dance version or adaptation of the other 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c75715d48190ac55713de9d5ba4f |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:57 p.m.