Triple
T31289469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAFKAP |
E797893
|
entity |
| Predicate | refersToNotableWork |
P136156
|
FINISHED |
| Object | Purple Rain |
—
|
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: Purple Rain | Statement: [TAFKAP, refersToNotableWork, Purple Rain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToNotableWork Context triple: [TAFKAP, refersToNotableWork, Purple Rain]
-
A.
refersToNotableTitle
Indicates that one entity refers to a notable or distinguished title held or used by another entity.
-
B.
notableWorkWith
Indicates a relationship where two or more entities are recognized for having collaborated on or been jointly associated with a significant work or project.
-
C.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
D.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
E.
notableFromWork
chosen
Indicates that an entity is notable or well-known specifically because of a particular work it created, contributed to, or is associated with.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 29, 2026, 9:14 p.m.