Triple
T34138962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morray |
E875653
|
entity |
| Predicate | featuredOnArtist |
P71140
|
FINISHED |
| Object | J. Cole |
E49779
|
NE 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: J. Cole | Statement: [Morray, featuredOnArtist, J. Cole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredOnArtist Context triple: [Morray, featuredOnArtist, J. Cole]
-
A.
hasFeaturedArtist
Indicates that an entity (such as a song or track) includes another artist who appears as a featured performer.
-
B.
featuredOnSong
chosen
Indicates that an entity (such as an artist) appears as a guest or secondary contributor on a particular song.
-
C.
featuresArtistAs
Indicates that one entity includes or presents another entity in the role of an artist (e.g., a work, event, or product featuring a specific artist).
-
D.
featuredArtistLiveVersion
Indicates that an artist is the prominently credited performer on a live-recorded version of a work.
-
E.
featuresVariousArtists
Indicates that something (typically a creative work) includes contributions from multiple distinct artists rather than a single primary artist.
- F. None of above.
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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a030713bd2881908bcc69e7d1e9fd09 |
completed | May 12, 2026, 10:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36c1c4e3708190a3921a46a09b0e80 |
completed | June 20, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_6a0304c29abc819085ffd17ab9a8c844 |
completed | May 12, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:53 a.m.