Triple
T9458133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carabosse |
E228069
|
entity |
| Predicate | typicalPortrayalInBallet |
P32690
|
FINISHED |
| Object | often danced by a male performer en travesti |
—
|
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: often danced by a male performer en travesti | Statement: [Carabosse, typicalPortrayalInBallet, often danced by a male performer en travesti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPortrayalInBallet Context triple: [Carabosse, typicalPortrayalInBallet, often danced by a male performer en travesti]
-
A.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
B.
balletInActs
Indicates that a ballet is structured or divided into a specified number of acts.
-
C.
danceRole
chosen
Indicates that one entity has a specific role or function within a dance performed with or in relation to another entity.
-
D.
balletInclusion
Indicates that ballet is included, featured, or incorporated as a component within something, such as a program, event, or curriculum.
-
E.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f924f3081909dd937cbe6802881 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.