Triple
T32376840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomboy (Destiny Rogers song) |
E827309
|
entity |
| Predicate | producerCollectiveMember |
P69875
|
FINISHED |
| Object | The Stereotypes |
—
|
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: The Stereotypes | Statement: [Tomboy (Destiny Rogers song), producerCollectiveMember, The Stereotypes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerCollectiveMember Context triple: [Tomboy (Destiny Rogers song), producerCollectiveMember, The Stereotypes]
-
A.
producedMember
Indicates that one entity created, manufactured, or generated another entity as its product or output.
-
B.
associatedProducerCollective
chosen
Indicates a relationship where an entity is linked to, or works in connection with, a specific producer collective.
-
C.
producerAssociation
Indicates a relationship where one entity is associated with or acts in the role of a producer for another entity or product.
-
D.
producerRoster
Indicates that an entity is included as a producer within a specified roster or lineup.
-
E.
producerOfWork
Indicates that one entity is the creator or originator responsible for producing a particular 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 1, 2026, 12:51 a.m.