Triple
T4031667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodeo (ballet) |
E83725
|
entity |
| Predicate | balletInScenes |
P32701
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Rodeo (ballet), balletInScenes, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balletInScenes Context triple: [Rodeo (ballet), balletInScenes, 5]
-
A.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
B.
balletInclusion
chosen
Indicates that ballet is included, featured, or incorporated as a component within something, such as a program, event, or curriculum.
-
C.
danceRole
Indicates that one entity has a specific role or function within a dance performed with or in relation to another entity.
-
D.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
E.
hasBalletMaster
Indicates that an entity is associated with or overseen by a specific ballet master responsible for its ballet-related training, direction, or instruction.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb0dbb8481909ff2ee49dadcd1dc |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.