Triple
T19584882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Hot Minute |
E490082
|
entity |
| Predicate | containsExperimentalTracks |
P111486
|
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: [One Hot Minute, containsExperimentalTracks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsExperimentalTracks Context triple: [One Hot Minute, containsExperimentalTracks, true]
-
A.
includesExperiment
Indicates that one entity contains or encompasses a specific experiment as part of its scope, composition, or content.
-
B.
hasExperimentalSound
chosen
Indicates that something possesses or exhibits an unconventional, innovative, or avant-garde sound quality or style.
-
C.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
D.
hasTrackFeatures
Indicates that something possesses or is associated with specific track-related characteristics or attributes.
-
E.
hasExperimentalHall
Indicates that an entity possesses or includes an experimental hall as part of its facilities or structure.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64050127c8190b93b8716a1a4ad81 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.