Triple
T1333498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mak Yong |
E28694
|
entity |
| Predicate | traditionalContext |
P15641
|
FINISHED |
| Object | village performances |
—
|
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: village performances | Statement: [Mak Yong, traditionalContext, village performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalContext Context triple: [Mak Yong, traditionalContext, village performances]
-
A.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
B.
traditionalStatus
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
-
C.
traditionalOrigin
chosen
Indicates that something comes from, or is rooted in, a long-established cultural or customary source or practice.
-
D.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
E.
traditionalLanguageName
Indicates the name traditionally used in a particular language to refer to the subject 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1e98900819092c54c0fb58b958a |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.