Triple
T18683256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | malong |
E456786
|
entity |
| Predicate | usedInDance |
P132277
|
FINISHED |
| Object | kapa malong-malong |
—
|
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: kapa malong-malong | Statement: [malong, usedInDance, kapa malong-malong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDance Context triple: [malong, usedInDance, kapa malong-malong]
-
A.
usesDanceForms
Indicates that one entity employs or incorporates specific dance forms in its actions, practices, or expressions.
-
B.
hasDanceInfluence
Indicates that one entity has contributed to shaping, inspiring, or affecting the dance style, technique, or choreography of another entity.
-
C.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
D.
hasDanceMovement
Indicates that one entity includes, performs, or is characterized by a specific dance movement associated with another entity.
-
E.
hasDanceMove
Indicates that an entity performs, demonstrates, or is associated with a particular dance move.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2abf3c8190958c03066b5814af |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.