Triple
T29847597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lieutenant of Inishmore |
E757971
|
entity |
| Predicate | firstLondonProductionAt |
P203232
|
FINISHED |
| Object | Garrick Theatre |
—
|
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: Garrick Theatre | Statement: [The Lieutenant of Inishmore, firstLondonProductionAt, Garrick Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLondonProductionAt Context triple: [The Lieutenant of Inishmore, firstLondonProductionAt, Garrick Theatre]
-
A.
firstPerformanceProduction
Indicates that a production is the one in which a work (e.g., a play, musical, or performance piece) was first publicly performed.
-
B.
firstBroadwayProductionTheatre
Indicates the theatre where an entity’s first Broadway production was staged.
-
C.
firstPerformanceTheatre
Indicates the theatre where an entity (such as a play or performance) was first performed.
-
D.
theatricalProductionPremiereYear
Indicates the year in which a theatrical production was first premiered or publicly performed.
-
E.
originalLondonProductionYear
Indicates the year in which the work’s original production or premiere took place in London.
- F. None of above. chosen
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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
| PDg | Predicate description generation | batch_6a013f08f77c8190b5305c1b700c4840 |
completed | May 11, 2026, 2:29 a.m. |
Created at: April 29, 2026, 5:42 p.m.