Triple
T31799367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh! Calcutta! |
E811685
|
entity |
| Predicate | broadwayTransferTheatre |
P35531
|
FINISHED |
| Object | Belasco Theatre |
—
|
NE NERFINISHED |
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: Belasco Theatre | Statement: [Oh! Calcutta!, broadwayTransferTheatre, Belasco Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadwayTransferTheatre Context triple: [Oh! Calcutta!, broadwayTransferTheatre, Belasco Theatre]
-
A.
broadwayTransfer
chosen
Indicates a transfer or move of a theatrical production or performance to a Broadway venue or run.
-
B.
offBroadwayTransferTheatre
Indicates that a theatrical production has transferred from another venue to an Off-Broadway theatre.
-
C.
broadwayOrWestEndTransfer
Indicates that a theatrical production has transferred between Broadway and London’s West End (in either direction).
-
D.
broadwayTheatreRenamed
Indicates that a Broadway theatre has undergone a name change from one official title to another.
-
E.
broadwayTheatreDistrict
Indicates that something is located in or associated with the Broadway Theatre District, the area known for its concentration of Broadway theaters and related activities.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 11:41 p.m.