Triple
T34661774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanya Tucker – While I'm Livin' (producer) |
E890130
|
entity |
| Predicate | roleForArtist |
P133932
|
FINISHED |
| Object | Tanya Tucker |
—
|
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: Tanya Tucker | Statement: [Tanya Tucker – While I'm Livin' (producer), roleForArtist, Tanya Tucker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleForArtist Context triple: [Tanya Tucker – While I'm Livin' (producer), roleForArtist, Tanya Tucker]
-
A.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
B.
documentsArtistRole
chosen
Indicates that something records or specifies the particular role an artist has in relation to a work or project.
-
C.
featuresArtistAs
Indicates that one entity includes or presents another entity in the role of an artist (e.g., a work, event, or product featuring a specific artist).
-
D.
selectedArtist
Indicates that a particular artist has been chosen or designated from a set of possible artists.
-
E.
subjectRelationToArtist
Indicates the nature of the relationship or connection that the subject has to the artist.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f33b2c8190a7ba07ecfc6ff281 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.