Triple
T28315361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Present |
E717118
|
entity |
| Predicate | associatedAuthorOfOtherWorks |
P154273
|
FINISHED |
| Object | Look Back in Anger |
—
|
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: Look Back in Anger | Statement: [Time Present, associatedAuthorOfOtherWorks, Look Back in Anger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAuthorOfOtherWorks Context triple: [Time Present, associatedAuthorOfOtherWorks, Look Back in Anger]
-
A.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
B.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
C.
hasAuthorOfOtherWork
chosen
Indicates that an entity is the author of another distinct work associated with the first entity.
-
D.
workByAuthorAlsoKnownFor
Indicates that a work is created by an author who is also notably recognized for another specified work or contribution.
-
E.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with another entity.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a01378bf05c8190af9f5e06a2810c7d |
completed | May 11, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_6a0137277c6c8190bcec341f2a0757c4 |
completed | May 11, 2026, 1:55 a.m. |
Created at: April 28, 2026, 12:19 a.m.