Triple
T33202013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukkabla |
E849925
|
entity |
| Predicate | hasNotableChoreography |
P35114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mukkabla, hasNotableChoreography, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableChoreography Context triple: [Mukkabla, hasNotableChoreography, true]
-
A.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
B.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
-
C.
hasChoreographicCharacteristics
Indicates that something possesses specific features, qualities, or attributes related to choreography or choreographic style.
-
D.
hasDanceSequences
chosen
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
E.
hasNotableChoreographerAssociation
Indicates a relationship where an entity is significantly associated with a particular choreographer, such as through collaboration, influence, or dedicated work.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a019037edbc8190bdaec436ac2fcec6 |
completed | May 11, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_6a018fe05a34819080068f588b5ff80c |
completed | May 11, 2026, 8:14 a.m. |
Created at: May 1, 2026, 1:30 a.m.