Triple
T19665490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bootleg Series Vol. 4: Bob Dylan Live 1966 |
E472187
|
entity |
| Predicate | famousHeckle |
P136871
|
FINISHED |
| Object | Judas! |
—
|
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: Judas! | Statement: [The Bootleg Series Vol. 4: Bob Dylan Live 1966, famousHeckle, Judas!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousHeckle Context triple: [The Bootleg Series Vol. 4: Bob Dylan Live 1966, famousHeckle, Judas!]
-
A.
oftenHeckledBy
Indicates that one entity frequently receives heckling, interruptions, or jeering from another entity.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
famousCall
Indicates that one entity makes a phone call to another entity who is widely known or celebrated.
-
D.
starMadeFamous
Indicates that one entity (such as a work, event, or role) is what caused another entity (typically a person) to become widely known or famous.
-
E.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416857c88190acb3adbf3e585fe5 |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.