Triple
T21169222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Festival 1983 Heavy Metal Day |
E521647
|
entity |
| Predicate | recordingsExist |
P22462
|
FINISHED |
| Object | archival video and audio recordings |
—
|
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: archival video and audio recordings | Statement: [US Festival 1983 Heavy Metal Day, recordingsExist, archival video and audio recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingsExist Context triple: [US Festival 1983 Heavy Metal Day, recordingsExist, archival video and audio recordings]
-
A.
recordingExists
chosen
Indicates that there is an existing recorded instance (such as audio, video, or other media) associated with the specified entities or event.
-
B.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
C.
recordingsFrom
Indicates a relationship where one entity serves as the source or origin of recordings that are associated with or derived from it.
-
D.
hasMultipleRecordings
Indicates that the same work, performance, or item exists in more than one distinct recorded version.
-
E.
hasRecordingHistory
Indicates that an entity has an associated record of past recordings or recorded events.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72711be9481909f16107b71d3500a |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.