Triple
T9248105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballet Russe de Monte Carlo |
E222248
|
entity |
| Predicate | artisticLineage |
P87776
|
FINISHED |
| Object | Russian Imperial Ballet tradition |
—
|
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: Russian Imperial Ballet tradition | Statement: [Ballet Russe de Monte Carlo, artisticLineage, Russian Imperial Ballet tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artisticLineage Context triple: [Ballet Russe de Monte Carlo, artisticLineage, Russian Imperial Ballet tradition]
-
A.
artisticField
Indicates the artistic domain or creative discipline in which an entity is active or associated.
-
B.
inspiredArtMovement
Indicates that one entity served as a creative or conceptual influence leading to the development or direction of an art movement in the other entity.
-
C.
artisticCharacteristic
Indicates that one entity possesses or exhibits a particular artistic quality, style, or trait in relation to another.
-
D.
inArtSince
Indicates that an entity has been involved or active in the field of art starting from a specified time.
-
E.
artMovement
Indicates the artistic movement or style with which an artwork, artist, or cultural work is associated.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05f6d62c8190a1e33f1854767b47 |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:31 p.m.