Triple
T20790700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Strange Records |
E511765
|
entity |
| Predicate | releasesFormat |
P59045
|
FINISHED |
| Object | vinyl records |
—
|
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: vinyl records | Statement: [Dr. Strange Records, releasesFormat, vinyl records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasesFormat Context triple: [Dr. Strange Records, releasesFormat, vinyl records]
-
A.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
-
B.
subsequentReleaseFormat
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
C.
formatReleased
chosen
Indicates that a particular release or version of something is made available in a specified format (such as digital, physical, or a specific file type).
-
D.
releases
Indicates that one entity causes something to be set free, emitted, or made available from its control or containment.
-
E.
releasesInclude
Indicates that a particular release or distribution contains, bundles, or makes available the specified component, item, or content.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c29010508190bf2cf577d7f64754 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.