Triple
T31930362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaleidoscope |
E815227
|
entity |
| Predicate | hasPhysicalReleaseFormat |
P85649
|
FINISHED |
| Object | CD |
—
|
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: CD | Statement: [Kaleidoscope, hasPhysicalReleaseFormat, CD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalReleaseFormat Context triple: [Kaleidoscope, hasPhysicalReleaseFormat, CD]
-
A.
hasReleaseMedium
chosen
Indicates the medium or format through which something (such as a work or product) is released or made available.
-
B.
hasPhysicalMedium
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
C.
physicalReleaseCharacteristic
Indicates a characteristic or property that describes some physical aspect or quality of a release (such as a product, media, or publication) in relation to that release.
-
D.
physicalReleaseDate
Indicates the calendar date on which a work is first made available in a tangible, physical format (e.g., disc, print, cartridge).
-
E.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:04 a.m.