Triple
T21442042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do It Again |
E528959
|
entity |
| Predicate | followsInSingleDiscography |
P113891
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Do It Again, followsInSingleDiscography, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInSingleDiscography Context triple: [Do It Again, followsInSingleDiscography, none]
-
A.
followsInDiscographyOf
Indicates that one musical release comes after another in the ordered sequence of works within the same artist’s discography.
-
B.
followsSingleFromAlbum
chosen
Indicates that a song is released as a single that follows another single from the same album in release sequence.
-
C.
precedesSingleInDiscography
Indicates that one musical single was released earlier than another within the same artist’s discography.
-
D.
hasPartInDiscographyOf
Indicates that one entity constitutes a component or item within the discography (recorded works catalog) of another entity.
-
E.
hasDiscographyType
Indicates that an entity’s discography is classified as a specific type (such as studio albums, live albums, compilations, etc.).
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b70322bc8190ae693163ededf5a0 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.