Triple
T6191476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cats |
E138399
|
entity |
| Predicate | originalWestEndTheatreRunStart |
P69576
|
FINISHED |
| Object | 1981-05-11 |
—
|
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: 1981-05-11 | Statement: [Cats, originalWestEndTheatreRunStart, 1981-05-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalWestEndTheatreRunStart Context triple: [Cats, originalWestEndTheatreRunStart, 1981-05-11]
-
A.
originalWestEndRunEnd
Indicates the date or point in time when a production’s original run in London’s West End concluded.
-
B.
numberOfWestEndPerformances
Indicates the total count of performances of a production that took place in London’s West End.
-
C.
notableWestEndRevivalTheatre
Indicates that the subject had a significant or well-known revival production staged in London’s West End theatre district.
-
D.
notableWestEndRevivalStart
Indicates the date or event when a notable revival production of a work began its run in London’s West End.
-
E.
originalWestEndDirector
Indicates that the subject served as the director of the original West End production of the referenced work.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0623ff0bc8190951512245a38f541 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:19 p.m.