Triple
T9051196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ca trù |
E216885
|
entity |
| Predicate | UNESCODomain |
P26544
|
FINISHED |
| Object | performing arts |
—
|
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: performing arts | Statement: [Ca trù, UNESCODomain, performing arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCODomain Context triple: [Ca trù, UNESCODomain, performing arts]
-
A.
UNESCORegion
Indicates that an entity is associated with, classified under, or belongs to a specific UNESCO-designated geographic region.
-
B.
UNESCOElement
chosen
Indicates that one entity is recognized as an element associated with UNESCO, such as being part of its heritage, cultural, or educational designations.
-
C.
UNESCOProgramme
Indicates that an entity is a program, initiative, or activity that is organized, sponsored, or officially recognized by UNESCO.
-
D.
roleWithUNESCO
Indicates that an entity holds or has held an official position, function, or recognized capacity in relation to UNESCO.
-
E.
UNESCOResolution
Indicates a formal decision, declaration, or recommendation adopted by UNESCO’s governing bodies regarding a specific issue, policy, or action.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b54423081908d9fd985109e336a |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.