Triple
T22655788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contact (Lincoln Center Theater production) |
E559221
|
entity |
| Predicate | openedOffBroadwayInYear |
P61121
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Contact (Lincoln Center Theater production), openedOffBroadwayInYear, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedOffBroadwayInYear Context triple: [Contact (Lincoln Center Theater production), openedOffBroadwayInYear, 1999]
-
A.
offBroadwayOpeningYear
chosen
Indicates the calendar year in which a production had its opening performance in an Off-Broadway venue.
-
B.
offBroadwayPremiereYear
Indicates the year in which a work (such as a play or musical) first premiered in an Off-Broadway production.
-
C.
hasBroadwayOpeningYearOfSource
Indicates that the Broadway production associated with the subject entity opened in the same year as specified by the source entity.
-
D.
offBroadwayOpeningDate
Indicates the date on which a production first opened in an Off-Broadway venue.
-
E.
BroadwayTransferYear
Indicates the year in which an entity was transferred to or began its run on Broadway.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765b93dc8190a0357dd4b6ae524a |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.