Triple
T31373933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big River |
E800238
|
entity |
| Predicate | revivalBroadwayTransfer |
P35531
|
FINISHED |
| Object | American Airlines 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: American Airlines Theatre | Statement: [Big River, revivalBroadwayTransfer, American Airlines Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalBroadwayTransfer Context triple: [Big River, revivalBroadwayTransfer, American Airlines Theatre]
-
A.
offBroadwayTransferTheatre
Indicates that a theatrical production has transferred from another venue to an Off-Broadway theatre.
-
B.
broadwayRevival
Indicates that a theatrical production is a new staging or restaging of a show on Broadway after its original Broadway run.
-
C.
broadwayTransfer
chosen
Indicates a transfer or move of a theatrical production or performance to a Broadway venue or run.
-
D.
revivedOffBroadway
Indicates that a theatrical production was brought back for a new run in an Off-Broadway venue after an earlier production or run.
-
E.
broadwayRevivalOpeningYear
Indicates the calendar year in which a specific Broadway revival production officially opened.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f69feac6c481908774e3f3104c0cf3 |
completed | May 3, 2026, 1:07 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:18 p.m.