Triple

T29679905
Position Surface form Disambiguated ID Type / Status
Subject Devils & Dust Tour E750920 entity
Predicate hasFanRecording P150088 FINISHED
Object audience bootlegs 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: audience bootlegs | Statement: [Devils & Dust Tour, hasFanRecording, audience bootlegs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFanRecording
Context triple: [Devils & Dust Tour, hasFanRecording, audience bootlegs]
  • A. hasLiveRecordingFrom chosen
    Indicates that a live recording was made of something (e.g., a work, performance, or event) at or from a specified source, venue, or occasion.
  • B. hasVideoRecording
    Indicates that there exists an associated video recording capturing or documenting the referenced entity or event.
  • C. hasWorkRecordingsOn
    Indicates that an entity has associated work recordings stored on or linked to another entity (such as a medium, platform, or system).
  • D. recordingOf
    Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
  • E. legendRecordedFrom
    Indicates that a legend or traditional story was documented or collected from a particular source, such as a person, group, or location.
  • 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_69f0d624d7b08190ba237d226f78d0d9 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
Created at: April 28, 2026, 7:09 p.m.