Triple
T33699746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table Manners |
E863420
|
entity |
| Predicate | firstWestEndProductionAt |
P203232
|
FINISHED |
| Object | Greenwich Theatre |
E863424
|
NE 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: Greenwich Theatre | Statement: [Table Manners, firstWestEndProductionAt, Greenwich Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWestEndProductionAt Context triple: [Table Manners, firstWestEndProductionAt, Greenwich Theatre]
-
A.
firstLondonProductionAt
chosen
Indicates that the subject had its first production or staging at a specified venue or location in London.
-
B.
originalWestEndTheatreRunStart
Indicates the date on which a production’s initial run in London’s West End first began.
-
C.
firstBroadwayProductionTheatre
Indicates the theatre where an entity’s first Broadway production was staged.
-
D.
originalWestEndProducer
Indicates that the subject served as a producer for the original West End production of the work or performance in question.
-
E.
theatricalProductionPremiereYear
Indicates the year in which a theatrical production was first premiered or publicly performed.
- F. None of above.
Provenance (4 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c9d90d08190bd892d3b72df967c |
completed | June 20, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:43 a.m.