Triple
T31448554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitri |
E802254
|
entity |
| Predicate | laterChoreographicVersionBy |
P195318
|
FINISHED |
| Object | Alexander Gorsky |
—
|
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: Alexander Gorsky | Statement: [Kitri, laterChoreographicVersionBy, Alexander Gorsky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterChoreographicVersionBy Context triple: [Kitri, laterChoreographicVersionBy, Alexander Gorsky]
-
A.
hasChoreographicRevisionsBy
chosen
Indicates that a work’s choreography has been revised or altered by a specified person or entity.
-
B.
hasChoreographicReconstructionBy
Indicates that a work’s choreography has been reconstructed or re-created by a specified person or entity.
-
C.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
-
D.
hasChoreographicSignatureOf
Indicates that something (such as a performance or movement sequence) bears the distinctive choreographic style, authorship, or creative imprint of a particular choreographer.
-
E.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
- 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_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: April 30, 2026, 9:11 p.m.