Triple
T35227238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bidesia dance |
E1017130
|
entity |
| Predicate | artFormComponent |
P182984
|
FINISHED |
| Object | dialogue |
—
|
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: dialogue | Statement: [Bidesia dance, artFormComponent, dialogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artFormComponent Context triple: [Bidesia dance, artFormComponent, dialogue]
-
A.
artForm
Indicates the type or category of artistic expression that characterizes or defines something (e.g., painting, music, dance).
-
B.
artFormCreated
Indicates that one entity is the creator or originator of a particular artistic form, style, or genre associated with the other entity.
-
C.
artFormIntegration
Indicates the incorporation or blending of one artistic form or medium into another within a unified creative work or practice.
-
D.
artFormIncludes
Indicates that a broader artistic category or practice encompasses or contains a particular art form as one of its components or examples.
-
E.
artFormOrigin
Indicates the place, culture, or context in which a particular art form first originated or developed.
- F. None of above. chosen
Provenance (4 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:02 p.m.