Triple
T19137738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nose (opera production) |
E468475
|
entity |
| Predicate | revivalSeasonAtMet |
P134578
|
FINISHED |
| Object | 2013 season |
—
|
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: 2013 season | Statement: [The Nose (opera production), revivalSeasonAtMet, 2013 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalSeasonAtMet Context triple: [The Nose (opera production), revivalSeasonAtMet, 2013 season]
-
A.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
B.
revivalStars
Indicates a relationship where one entity initiates, leads, or is central to a revival, renewal, or comeback of another entity.
-
C.
revivalEndTime
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
D.
reappearsIn
Indicates that an entity that previously appeared becomes present or visible again in the same or another context.
-
E.
revivalYear
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
- F. None of above. chosen
Provenance (4 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ee8b988190914ef21ca1b890c6 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.