Triple
T5229871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Change (song) |
E118080
|
entity |
| Predicate | releasedAsSingleIn |
P62507
|
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: [Change (song), releasedAsSingleIn, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedAsSingleIn Context triple: [Change (song), releasedAsSingleIn, 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.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
-
C.
isSingleFromAlbum
Indicates that a song is released as a single originating from a particular album.
-
D.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
-
E.
releasedMusicBy
Indicates that a musical work (such as a song, album, or EP) was issued or made publicly available by a particular artist or musical act.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd7aff0244819085c4799793ed0185 |
completed | March 20, 2026, 4:51 p.m. |
Created at: March 20, 2026, 1:48 p.m.