Triple
T34284854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanghalang Huseng Batute |
E879703
|
entity |
| Predicate | performanceStyleEmphasis |
P13362
|
FINISHED |
| Object | experimental |
—
|
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: experimental | Statement: [Tanghalang Huseng Batute, performanceStyleEmphasis, experimental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceStyleEmphasis Context triple: [Tanghalang Huseng Batute, performanceStyleEmphasis, experimental]
-
A.
effectEmphasis
Indicates that one entity highlights, intensifies, or draws special attention to the effect produced by another entity or action.
-
B.
performanceStyle
chosen
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
C.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
D.
accentStyle
Indicates the manner or pattern in which an entity’s accent or emphasis is applied or presented.
-
E.
stylisticEffect
Indicates the relationship where one element produces, contributes to, or embodies a particular stylistic impact or impression on another.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 1, 2026, 1:57 a.m.