Triple
T2521562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headbangers Ball |
E55533
|
entity |
| Predicate | originalRuntime |
P39601
|
FINISHED |
| Object | approximately 2–3 hours |
—
|
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: approximately 2–3 hours | Statement: [Headbangers Ball, originalRuntime, approximately 2–3 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRuntime Context triple: [Headbangers Ball, originalRuntime, approximately 2–3 hours]
-
A.
originalRunEra
Indicates the time period or era during which something (such as a show, series, or product) was first originally run or released.
-
B.
originalRelease
Indicates the initial publication or first official release event of a work or product.
-
C.
originalInstrumentation
Indicates the relationship between a musical work and the specific instruments or ensemble for which it was initially scored or conceived.
-
D.
originProgram
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
-
E.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2367b6c819094239dfd12399643 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1487e0c8190b90dcf30586ad4cd |
completed | March 7, 2026, 7:18 a.m. |
Created at: March 6, 2026, 9:46 p.m.