Triple
T26263210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marapu ceremonies |
E656907
|
entity |
| Predicate | involvesMusic |
P135837
|
FINISHED |
| Object | gong ensembles |
—
|
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: gong ensembles | Statement: [Marapu ceremonies, involvesMusic, gong ensembles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesMusic Context triple: [Marapu ceremonies, involvesMusic, gong ensembles]
-
A.
usesMusicFor
Indicates that one entity employs or applies music as a means, tool, or resource to achieve or support some purpose, activity, or effect for another entity or context.
-
B.
音楽
chosen
Indicates a relationship where an entity is associated with, involves, or is characterized by music as a form of sound-based artistic or cultural expression.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
musicAttracted
Indicates that one entity is drawn or attracted to another entity because of its music.
-
E.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 26, 2026, 9:10 p.m.