Triple
T23969625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desamuduru |
E604193
|
entity |
| Predicate | hasFightSequencesChoreographyBy |
P154075
|
FINISHED |
| Object | Vijayan |
—
|
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: Vijayan | Statement: [Desamuduru, hasFightSequencesChoreographyBy, Vijayan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFightSequencesChoreographyBy Context triple: [Desamuduru, hasFightSequencesChoreographyBy, Vijayan]
-
A.
hasFightSceneWith
Indicates that two entities participate together in a fight scene or combat sequence.
-
B.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
C.
hasChoreographicCharacteristics
Indicates that something possesses specific features, qualities, or attributes related to choreography or choreographic style.
-
D.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
-
E.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1db392c8190a1044b75b898243a |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:25 p.m.