Triple
T27838043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaceship (Remix) |
E703294
|
entity |
| Predicate | hasAdditionalArtists |
P175322
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Spaceship (Remix), hasAdditionalArtists, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalArtists Context triple: [Spaceship (Remix), hasAdditionalArtists, true]
-
A.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
-
B.
containsAdditionalTracksBeyond
Indicates that one entity includes more tracks or items than are present in another referenced set or version.
-
C.
hasAdditionalLyricsBy
Indicates that an entity (such as a musical work or track) includes extra or modified lyrics contributed by a specified person or group beyond the original lyricist.
-
D.
hasRemixArtistDescriptor
Indicates that an entity has an associated descriptor specifying the artist responsible for a remix version of it.
-
E.
hasAdditionalLyrics
Indicates that an entity (such as a song or track) includes extra or supplementary lyrics beyond a primary or original set.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 27, 2026, 6 p.m.