Triple
T5417405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rag Trade |
E121164
|
entity |
| Predicate | revivalFirstAired |
P34952
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [The Rag Trade, revivalFirstAired, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalFirstAired Context triple: [The Rag Trade, revivalFirstAired, 1977]
-
A.
notableRevivalPremiereDate
chosen
Indicates the date on which a notable revival or re-staging of a work (such as a play, musical, or performance) was first premiered.
-
B.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
C.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
D.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
E.
revivalHost
Indicates that one entity serves as the host or venue where a revival event, such as a renewed performance, series, or movement, takes place.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87e620f081909eb9a5e1f284e5a2 |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.