Triple
T35181610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It's Only a Play |
E1015864
|
entity |
| Predicate | 2014RevivalType |
P182364
|
FINISHED |
| Object | Broadway revival |
—
|
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: Broadway revival | Statement: [It's Only a Play, 2014RevivalType, Broadway revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2014RevivalType Context triple: [It's Only a Play, 2014RevivalType, Broadway revival]
-
A.
2014RevivalTheatre
chosen
Indicates a relationship where an entity is associated with a theatrical revival production that took place in 2014.
-
B.
revivalVersionProducedFor
Indicates that a specific version of a revived work (such as a reboot, remake, or updated edition) was produced for a particular entity, context, or release.
-
C.
revivalVersionAssociatedWith
Indicates that one version or edition is linked to its corresponding revival or reissued version.
-
D.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
E.
2022RevivalCity
Indicates a relationship where an entity is associated with a city that experienced a notable revival or renewal in the year 2022.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.