Triple
T25581361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolin’ Out |
E641248
|
entity |
| Predicate | hasArtistAssociation |
P104092
|
FINISHED |
| Object | The Temptations |
—
|
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 Temptations | Statement: [Coolin’ Out, hasArtistAssociation, The Temptations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistAssociation Context triple: [Coolin’ Out, hasArtistAssociation, The Temptations]
-
A.
musicalArtistAssociated
chosen
Indicates a relationship where one musical artist is professionally connected or affiliated with another, such as through collaboration, membership, or frequent association.
-
B.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
-
C.
associatedWithArtistHeritage
Indicates a relationship where an entity is connected to, derived from, or meaningfully linked with an artist’s cultural, ethnic, or historical heritage.
-
D.
associatedWithArtistType
Indicates that an entity has a connection or linkage to a particular category or type of artist.
-
E.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 4:12 p.m.