Triple
T20868163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell Freezes Over |
E513818
|
entity |
| Predicate | featuresAcousticVersions |
P89096
|
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: [Hell Freezes Over, featuresAcousticVersions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAcousticVersions Context triple: [Hell Freezes Over, featuresAcousticVersions, true]
-
A.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
-
B.
hasAcousticDemoVersion
chosen
Indicates that an entity has a version or recording presented in an acoustic demo form.
-
C.
isAcoustic
Indicates that something produces sound using natural resonance or mechanical vibration rather than electronic amplification or synthesis.
-
D.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
E.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c46174a08190bf4ffd2683e15d78 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.