Triple
T20143135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peresean war dance |
E491224
|
entity |
| Predicate | traditionallyPracticedBy |
P10364
|
FINISHED |
| Object | Sasak men |
—
|
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: Sasak men | Statement: [Peresean war dance, traditionallyPracticedBy, Sasak men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPracticedBy Context triple: [Peresean war dance, traditionallyPracticedBy, Sasak men]
-
A.
traditionsMaintainedBy
Indicates that certain traditions are preserved, upheld, or continued in practice by a particular entity.
-
B.
practicedTradition
Indicates that an entity engages in or carries out a particular tradition as a customary or repeated practice.
-
C.
isPracticedBy
chosen
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
D.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
E.
practicedMedicineOfTradition
Indicates that an entity engaged in the medical practices or healing methods associated with a particular cultural or traditional system.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679cbc388190bb2b444a69a597a6 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.