Triple
T9051303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hát chèo |
E216887
|
entity |
| Predicate | modernContext |
P3657
|
FINISHED |
| Object | performed in professional theatres |
—
|
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: performed in professional theatres | Statement: [Hát chèo, modernContext, performed in professional theatres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernContext Context triple: [Hát chèo, modernContext, performed in professional theatres]
-
A.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
B.
modernExample
Indicates that something serves as a contemporary or current-day instance or illustration of something else.
-
C.
modernUse
chosen
Indicates how something is currently used or applied in modern times.
-
D.
majorContext
Indicates that one entity serves as the primary or most significant contextual framework within which the other entity is understood or interpreted.
-
E.
modernInterpretation
Indicates that one entity is a contemporary or updated interpretation, reading, or understanding of another 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_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.