Triple
T23614320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Predict a Riot |
E583133
|
entity |
| Predicate | chorusCharacterizedAs |
P662
|
FINISHED |
| Object | energetic |
—
|
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: energetic | Statement: [I Predict a Riot, chorusCharacterizedAs, energetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chorusCharacterizedAs Context triple: [I Predict a Riot, chorusCharacterizedAs, energetic]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
chorusType
Indicates the specific kind or category of chorus associated with an entity (e.g., type of vocal ensemble or choral grouping).
-
C.
chorusFeature
Indicates that one entity participates in or is highlighted within the chorus section of another entity, such as a song or musical piece.
-
D.
chorus
Indicates that multiple entities jointly produce or participate in a coordinated vocal or expressive performance, typically as a unified group.
-
E.
allyOfCharacter
Indicates that one character maintains an alliance or supportive partnership with another character.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0f71a2481909c3d0d8d0d58e20f |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:45 p.m.