Triple
T31448552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitri |
E802254
|
entity |
| Predicate | balletComposer |
P137010
|
FINISHED |
| Object | Ludwig Minkus |
—
|
NE NERFINISHED |
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: Ludwig Minkus | Statement: [Kitri, balletComposer, Ludwig Minkus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balletComposer Context triple: [Kitri, balletComposer, Ludwig Minkus]
-
A.
originalBalletComposer
chosen
Indicates that a person is the composer who created the original musical score for a particular ballet.
-
B.
balletsRussesProduction
Indicates that one entity is a production created or staged by the Ballets Russes company in relation to another entity.
-
C.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
D.
notableBallet
Indicates that there is a notable or significant ballet associated with the subject.
-
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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:11 p.m.