Triple
T32419407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Chop on the Beat |
E828410
|
entity |
| Predicate | featuresRoleOfCreator |
P13180
|
FINISHED |
| Object | record producer |
—
|
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: record producer | Statement: [Young Chop on the Beat, featuresRoleOfCreator, record producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRoleOfCreator Context triple: [Young Chop on the Beat, featuresRoleOfCreator, record producer]
-
A.
featuresAuthor
Indicates that something includes or highlights a particular author as a primary associated contributor.
-
B.
creatorType
chosen
Indicates the role or category of a creator in relation to the creation of something (e.g., author, artist, director).
-
C.
featuresCreator
Indicates that an entity prominently presents, highlights, or showcases a particular creator as a key associated party.
-
D.
creatorField
Indicates that one entity is recorded as the creator or originator of another entity within a specific field or context.
-
E.
possibleCreator
Indicates that an entity is a plausible but not definitively confirmed creator or originator of another entity.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0115fb84448190b8b67a5ace7b289a |
completed | May 10, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a0114ef60a081908f8db7868cf29b2f |
completed | May 10, 2026, 11:29 p.m. |
Created at: May 1, 2026, 12:54 a.m.