Triple
T36273042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Meal |
E892726
|
entity |
| Predicate | notableProductionTheatre |
P190988
|
FINISHED |
| Object | Playwrights Horizons |
E517108
|
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: Playwrights Horizons | Statement: [The Big Meal, notableProductionTheatre, Playwrights Horizons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProductionTheatre Context triple: [The Big Meal, notableProductionTheatre, Playwrights Horizons]
-
A.
notableTheatre
Indicates that there is a notable or significant theatre associated with the subject entity.
-
B.
notableTheaterWork
Indicates that a theater work is notably associated with, or a significant part of the achievements of, a given entity.
-
C.
notablePlaywrightProduced
Indicates that a notable playwright created or authored the referenced play or dramatic work.
-
D.
notableTheater
Indicates that there is a significant or well-known theater associated with the subject.
-
E.
notableProductionPresented
chosen
Indicates that a particular production has been prominently presented or staged by a given entity, such as a venue, company, or organization.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a31179cc8190b2e28183c2904ed3 |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.