Triple
T14675682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonderful Life |
E344637
|
entity |
| Predicate | reReleaseType |
P3286
|
FINISHED |
| Object | major-label single |
—
|
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: major-label single | Statement: [Wonderful Life, reReleaseType, major-label single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reReleaseType Context triple: [Wonderful Life, reReleaseType, major-label single]
-
A.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
B.
reReleaseLabel
Indicates that a work has been re-released under a different label than its original release.
-
C.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
D.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
E.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5666e648190b5faa07076f497b8 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.