Triple
T15193949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroes and Villains |
E363095
|
entity |
| Predicate | usesUnconventionalSongForm |
P9125
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Heroes and Villains, usesUnconventionalSongForm, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesUnconventionalSongForm Context triple: [Heroes and Villains, usesUnconventionalSongForm, true]
-
A.
hasSpecialSong
Indicates that one entity possesses or is associated with a particular song that is unique, distinctive, or specially designated for it.
-
B.
hasLyricalForm
Indicates that one entity (typically a musical or poetic work) possesses or is characterized by a particular lyrical structure or form.
-
C.
notableSongCharacteristic
chosen
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
D.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
E.
isOftenSungToTune
Indicates that one song or piece of text is frequently performed using the melody or musical setting of another.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067eb710819085211fd05d5fa5f0 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.