Triple
T35567769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faden Away |
E1027823
|
entity |
| Predicate | featuresArtistUnderName |
P131921
|
FINISHED |
| Object | Snoopzilla |
E1027820
|
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: Snoopzilla | Statement: [Faden Away, featuresArtistUnderName, Snoopzilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresArtistUnderName Context triple: [Faden Away, featuresArtistUnderName, Snoopzilla]
-
A.
featuresArtistFromRegion
Indicates that something includes or highlights an artist whose origin or affiliation is with a specified geographic region.
-
B.
featuresArtistAsRecordingArtist
Indicates that an item (such as a recording or release) includes a particular artist in the role of the recording artist.
-
C.
featuresArtistAs
chosen
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.
featuresArtistTransitionTo
Indicates a change in the featured artist on a work, marking the transition from one featured artist to another.
-
E.
selectedArtist
Indicates that a particular artist has been chosen or designated from a set of possible artists.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389c02049c8190b7103e2c0fc73f95 |
completed | June 22, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.