Triple
T38405616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call Me Anna |
E901319
|
entity |
| Predicate | subjectAwardWork |
P15639
|
FINISHED |
| Object | The Miracle Worker |
—
|
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 Miracle Worker | Statement: [Call Me Anna, subjectAwardWork, The Miracle Worker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAwardWork Context triple: [Call Me Anna, subjectAwardWork, The Miracle Worker]
-
A.
awardRelatedWork
Indicates that there is a connection between an award and the work (such as a project, publication, or performance) for which it was given or with which it is associated.
-
B.
awardReceivedByWork
chosen
Indicates that a particular award was given in recognition of a specific work (such as a book, film, or artwork).
-
C.
awardContributedTo
Indicates that an entity played a role or made a contribution that helped lead to a particular award or recognition being granted.
-
D.
categoryOfAwardedWork
Indicates the category or type of work for which an award is given.
-
E.
authorAwardedForBodyOfWork
Indicates that an author received an award recognizing their entire body of work rather than a single specific piece.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:31 p.m.