Triple
T30352759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamebread |
E772045
|
entity |
| Predicate | primaryArtistFocus |
P7867
|
FINISHED |
| Object | 2 Chainz |
E40049
|
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: 2 Chainz | Statement: [Gamebread, primaryArtistFocus, 2 Chainz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArtistFocus Context triple: [Gamebread, primaryArtistFocus, 2 Chainz]
-
A.
primaryArtist
chosen
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
B.
primaryInstrumentalFocus
Indicates that one entity serves as the main or most emphasized instrument or means by which another entity performs an action or achieves an effect.
-
C.
primaryArtistClient
Indicates that the referenced client is the main or principal artist associated with a given work, project, or relationship.
-
D.
primaryArtistNationality
Indicates the nationality associated with the main or primary artist involved in a work or context.
-
E.
featuresPrimaryInstrument
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a020ec13d808190b41acdc31adc4191 |
completed | May 11, 2026, 5:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27893115908190a27bd52d7a563c0d |
completed | June 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_6a020d9259c08190ad0370091c23ea8a |
completed | May 11, 2026, 5:10 p.m. |
Created at: April 29, 2026, 7:56 p.m.