Triple
T34428203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Relatively Speaking |
E883747
|
entity |
| Predicate | firstBroadwayRunOpeningDate |
P40638
|
FINISHED |
| Object | 2011-10-20 |
—
|
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: 2011-10-20 | Statement: [Relatively Speaking, firstBroadwayRunOpeningDate, 2011-10-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBroadwayRunOpeningDate Context triple: [Relatively Speaking, firstBroadwayRunOpeningDate, 2011-10-20]
-
A.
originalBroadwayOpeningDate
chosen
Indicates the calendar date on which a production first opened on Broadway in its original run.
-
B.
firstBroadwayProductionYear
Indicates the calendar year in which an entity’s first production was staged on Broadway.
-
C.
preBroadwayOpeningDate
Indicates the date on which a production had its opening performance prior to its official Broadway run.
-
D.
hasBroadwayOpeningYearOfSource
Indicates that the Broadway production associated with the subject entity opened in the same year as specified by the source entity.
-
E.
offBroadwayPremiereYear
Indicates the year in which a work (such as a play or musical) first premiered in an Off-Broadway production.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.