Triple
T28197722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tide Is High (Get the Feeling) |
E716490
|
entity |
| Predicate | previousNotableVersionArtist |
P78035
|
FINISHED |
| Object | Blondie |
—
|
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: Blondie | Statement: [The Tide Is High (Get the Feeling), previousNotableVersionArtist, Blondie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNotableVersionArtist Context triple: [The Tide Is High (Get the Feeling), previousNotableVersionArtist, Blondie]
-
A.
notableVersionArtist
chosen
Indicates that an artist is notably associated with a particular version or rendition of a work, such as a song, recording, or performance.
-
B.
previousArtistName
Indicates that an artist previously used a different name before adopting their current one.
-
C.
previousTitleArtist
Indicates that the subject artist held the same title or role immediately before the referenced artist.
-
D.
notableFormerArtist
Indicates that the subject was previously an artist associated with the object and is recognized as notable in that former artistic role.
-
E.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 27, 2026, 10:29 p.m.