Triple
T3857690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Winnipeg Ballet |
E90057
|
entity |
| Predicate | hasBalletMaster |
P52382
|
FINISHED |
| Object | various |
—
|
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: various | Statement: [Royal Winnipeg Ballet, hasBalletMaster, various]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalletMaster Context triple: [Royal Winnipeg Ballet, hasBalletMaster, various]
-
A.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
B.
balletInclusion
Indicates that ballet is included, featured, or incorporated as a component within something, such as a program, event, or curriculum.
-
C.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
-
D.
balletCompany
Indicates that one entity is a ballet company associated with, representing, or responsible for another entity (such as a performance, dancer, or production).
-
E.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec09312c81908ffd7441c83730c8 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:19 p.m.