Triple
T9236762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Cry Now |
E221955
|
entity |
| Predicate | hasFormatRelease |
P59045
|
FINISHED |
| Object | vinyl LP |
—
|
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 LP | Statement: [Don't Cry Now, hasFormatRelease, vinyl LP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormatRelease Context triple: [Don't Cry Now, hasFormatRelease, vinyl LP]
-
A.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
-
B.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
C.
subsequentReleaseFormat
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
D.
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).
-
E.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09e553081909cf864635cfc5dcc |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.