Triple
T15202217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Being Alive |
E363295
|
entity |
| Predicate | broadwayRevivalInclusion |
P4738
|
FINISHED |
| Object | 1995 Broadway revival of Company |
—
|
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: 1995 Broadway revival of Company | Statement: [Being Alive, broadwayRevivalInclusion, 1995 Broadway revival of Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadwayRevivalInclusion Context triple: [Being Alive, broadwayRevivalInclusion, 1995 Broadway revival of Company]
-
A.
broadwayRevival
chosen
Indicates that a theatrical production is a new staging or restaging of a show on Broadway after its original Broadway run.
-
B.
broadwayTheatreRenamed
Indicates that a Broadway theatre has undergone a name change from one official title to another.
-
C.
revivedOffBroadway
Indicates that a theatrical production was brought back for a new run in an Off-Broadway venue after an earlier production or run.
-
D.
appearedInBroadwayProduction
Indicates that an entity participated as part of a Broadway stage production of another work or show.
-
E.
hasBroadwayProduction
Indicates that a work or show has been produced and staged in a Broadway theater.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b588b88190a88e91d521acbdfe |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97ee9d881908711dbe12a55283c |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.