Triple
T23651570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K.I.D.S. |
E584180
|
entity |
| Predicate | reReleaseFormat |
P97671
|
FINISHED |
| Object | commercial streaming release |
—
|
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: commercial streaming release | Statement: [K.I.D.S., reReleaseFormat, commercial streaming release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reReleaseFormat Context triple: [K.I.D.S., reReleaseFormat, commercial streaming release]
-
A.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
B.
subsequentReleaseFormat
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
C.
reissuedOnFormat
chosen
Indicates that an item has been reissued in a particular format or medium.
-
D.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
E.
reReleaseLabel
Indicates that a work has been re-released under a different label than its original release.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b358ce448190a654d2cd3e81ef83 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.