Triple
T21555712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inori |
E531884
|
entity |
| Predicate | soloistRole |
P144227
|
FINISHED |
| Object | performing stylized ritual gestures |
—
|
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: performing stylized ritual gestures | Statement: [Inori, soloistRole, performing stylized ritual gestures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soloistRole Context triple: [Inori, soloistRole, performing stylized ritual gestures]
-
A.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
B.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
C.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
D.
isSoloPerformance
Indicates that the performance is carried out by a single performer without accompaniment or participation from others.
-
E.
musicalEnsembleRole
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2df48c88190894b6b08a5cb6390 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.