Triple
T18744315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theatre for a New Audience at Polonsky Shakespeare Center |
E458367
|
entity |
| Predicate | typeOfWorkPresented |
P1366
|
FINISHED |
| Object | theatre productions |
—
|
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: theatre productions | Statement: [Theatre for a New Audience at Polonsky Shakespeare Center, typeOfWorkPresented, theatre productions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWorkPresented Context triple: [Theatre for a New Audience at Polonsky Shakespeare Center, typeOfWorkPresented, theatre productions]
-
A.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
B.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
C.
typeOfProject
Indicates the specific category or kind of project that an entity is associated with or classified under.
-
D.
thesisType
Indicates the specific category or kind of thesis associated with an academic work or degree.
-
E.
publicationTypeOfPresenter
Indicates the type or category of publication associated with a given presenter.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e57691c8688190b225cbd88493d9d1 |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.