Triple
T20585910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anything Goes (1934 Broadway musical) |
E505785
|
entity |
| Predicate | hasWestEndRevival |
P54465
|
FINISHED |
| Object | 1989 London revival |
—
|
LITERAL FINISHED |
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: 1989 London revival | Statement: [Anything Goes (1934 Broadway musical), hasWestEndRevival, 1989 London revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWestEndRevival Context triple: [Anything Goes (1934 Broadway musical), hasWestEndRevival, 1989 London revival]
-
A.
notableWestEndRevivalStart
Indicates the date or event when a notable revival production of a work began its run in London’s West End.
-
B.
hasWestEndRun
chosen
Indicates that a production or performance has been staged in London’s West End theatre district.
-
C.
notableWestEndRevivalTheatre
Indicates that the subject had a significant or well-known revival production staged in London’s West End theatre district.
-
D.
originalWestEndRunEnd
Indicates the date or point in time when a production’s original run in London’s West End concluded.
-
E.
numberOfWestEndPerformances
Indicates the total count of performances of a production that took place in London’s West End.
- 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a976bca4819086a4949e299159b5 |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.