Triple
T15202219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Being Alive |
E363295
|
entity |
| Predicate | westEndProductionInclusion |
P4739
|
FINISHED |
| Object | 1995 London revival of Company |
—
|
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: 1995 London revival of Company | Statement: [Being Alive, westEndProductionInclusion, 1995 London revival of Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westEndProductionInclusion Context triple: [Being Alive, westEndProductionInclusion, 1995 London revival of Company]
-
A.
westEndProduction
chosen
Indicates that one entity is a theatrical production that was staged in London’s West End, associated with the other entity (such as a play, musical, or venue).
-
B.
westEndOpeningDate
Indicates the calendar date on which a production or event first opened in London’s West End.
-
C.
westEndPremiereYear
Indicates the year in which a work first premiered in London’s West End.
-
D.
originalWestEndRunEnd
Indicates the date or point in time when a production’s original run in London’s West End concluded.
-
E.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b588b88190a88e91d521acbdfe |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.