Triple
T34291231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Miller Theatre |
E879893
|
entity |
| Predicate | hasNamesakeNotableWork |
P19293
|
FINISHED |
| Object | Death of a Salesman |
—
|
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: Death of a Salesman | Statement: [Arthur Miller Theatre, hasNamesakeNotableWork, Death of a Salesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeNotableWork Context triple: [Arthur Miller Theatre, hasNamesakeNotableWork, Death of a Salesman]
-
A.
namedForNotableWork
chosen
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
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.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that entity.
-
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.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 1, 2026, 1:57 a.m.