Triple
T23546461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "I'm a Hustla" |
E577906
|
entity |
| Predicate | hasNotableProducerTag |
P152746
|
FINISHED |
| Object | Swizz Beatz producer tag |
—
|
LITERAL 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: Swizz Beatz producer tag | Statement: ["I'm a Hustla", hasNotableProducerTag, Swizz Beatz producer tag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProducerTag Context triple: ["I'm a Hustla", hasNotableProducerTag, Swizz Beatz producer tag]
-
A.
hasNotableSegment
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
-
B.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
C.
hasNotableHead
Indicates that an entity is associated with a particularly prominent or distinguished leader or chief figure.
-
D.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
E.
hasNotablePromoter
Indicates that an entity is actively supported, publicized, or championed by a notable promoter.
- F. None of above. chosen
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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecb567c8190a54d2c3b63282af5 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:11 p.m.