Triple
T35407793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stay |
E1023412
|
entity |
| Predicate | primaryArtistCredit |
P7867
|
FINISHED |
| Object | Rufus and Chaka Khan |
E327219
|
NE 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: Rufus and Chaka Khan | Statement: [Stay, primaryArtistCredit, Rufus and Chaka Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArtistCredit Context triple: [Stay, primaryArtistCredit, Rufus and Chaka Khan]
-
A.
primaryArtist
chosen
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
B.
originalArtistNameCredit
Indicates that the credited name refers to the artist who originally created the work or recording.
-
C.
artistNameCredit
Indicates that a specific artist is credited by name for their contribution to a work or production.
-
D.
producerArtist
Indicates that one entity serves as the producer (e.g., overseeing or managing the creation) of a work created or performed by the artist entity.
-
E.
parentArtist
Indicates that one artist is the parent (biological, adoptive, or otherwise recognized) of another artist.
- F. None of above.
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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a386831cf288190b86792ac8025cd4d |
completed | June 21, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.