Triple
T5229824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tones of Home |
E118079
|
entity |
| Predicate | reReleaseAsSingle |
P36217
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Tones of Home, reReleaseAsSingle, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reReleaseAsSingle Context triple: [Tones of Home, reReleaseAsSingle, 1993]
-
A.
releasedAsSingleFor
Indicates that a particular track or song was issued as a standalone single specifically to promote or represent a given album, project, or release.
-
B.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
C.
reReleaseDate
chosen
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
D.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
E.
releasedSpecial
Indicates that an entity has issued or made available a special version, edition, or release of something.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0093a88190aba381ba3f761408 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.