Triple
T23391359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario Mims |
E594025
|
entity |
| Predicate | hasSignedArtist |
P16560
|
FINISHED |
| Object | Moneybagg Yo |
—
|
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: Moneybagg Yo | Statement: [Mario Mims, hasSignedArtist, Moneybagg Yo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignedArtist Context triple: [Mario Mims, hasSignedArtist, Moneybagg Yo]
-
A.
signedByArtist
Indicates that an item, such as a work or object, bears the authentic signature of the specified artist.
-
B.
signedArtist
chosen
Indicates that an artist has entered into a formal contract or agreement with a label, company, or representative.
-
C.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
-
D.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
E.
hasSignatureSong
Indicates that an artist or performer is especially associated with a particular song that is widely recognized as their defining or most iconic work.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49ca5a0819091b74ca59e7fedd4 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.