Triple
T38513945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dry as a Bone |
E921988
|
entity |
| Predicate | chronologyNextRelease |
P23879
|
FINISHED |
| Object | Rehab Doll |
—
|
NE NERFINISHED |
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: Rehab Doll | Statement: [Dry as a Bone, chronologyNextRelease, Rehab Doll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyNextRelease Context triple: [Dry as a Bone, chronologyNextRelease, Rehab Doll]
-
A.
chronologyNextPlannedRelease
Indicates that one release is the immediately following planned release in the chronological sequence of releases for another release.
-
B.
chronologyNextPublicationDate
Indicates that one publication directly follows another in time, specifying the date on which the subsequent publication occurs.
-
C.
chronologyNextAlbum
chosen
Indicates that one album directly follows another in chronological release order within an artist’s discography.
-
D.
laterReleases
Indicates that one release, version, or publication occurs after another in time.
-
E.
chronologyNextTitle
Indicates that one item is immediately followed by another item as the next title in a chronological sequence.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 3, 2026, 4:32 p.m.