Triple
T35567890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Wit Me |
E1027827
|
entity |
| Predicate | hasArtistAliasUsed |
P84992
|
FINISHED |
| Object | Snoopzilla |
—
|
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: Snoopzilla | Statement: [High Wit Me, hasArtistAliasUsed, Snoopzilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistAliasUsed Context triple: [High Wit Me, hasArtistAliasUsed, Snoopzilla]
-
A.
hasMusicalAlias
chosen
Indicates that an entity is known or performs under an alternative musical name or stage name.
-
B.
hasArtistLegalName
Indicates that an artist entity is associated with a specific legal (real) name used for official or formal purposes.
-
C.
hasArtistCurrentName
Indicates that the specified name is the artist’s current, officially used name.
-
D.
hasArtistLaterKnownFor
Indicates that an entity is associated with an artist who, at a later time, became notably known or recognized under that identity.
-
E.
associatedWithArtistNickname
Indicates that an entity is connected to or identified by a particular artist’s nickname or pseudonym.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:04 p.m.