Triple
T29721328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dance of the Earth |
E752060
|
entity |
| Predicate | associatedWorkChoreographer |
P12049
|
FINISHED |
| Object | Vaslav Nijinsky |
E213677
|
NE 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: Vaslav Nijinsky | Statement: [Dance of the Earth, associatedWorkChoreographer, Vaslav Nijinsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkChoreographer Context triple: [Dance of the Earth, associatedWorkChoreographer, Vaslav Nijinsky]
-
A.
hasChoreographer
chosen
Indicates that one entity serves as the choreographer responsible for designing or directing the movement or dance for another entity.
-
B.
coChoreographerWith
Indicates that two or more individuals share responsibility for choreographing the same work or performance together.
-
C.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
-
D.
associatedWorkComposer
Indicates that a person or entity is the composer responsible for creating the associated work.
-
E.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
- F. None of above.
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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26f1afd5048190b5172b005c8d2d46 |
completed | June 8, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:36 p.m.