Triple
T20418578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Among My Souvenirs |
E500780
|
entity |
| Predicate | hasNotableEraOfRevival |
P48377
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Among My Souvenirs, hasNotableEraOfRevival, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEraOfRevival Context triple: [Among My Souvenirs, hasNotableEraOfRevival, 1950s]
-
A.
notableRevival
Indicates that something has undergone a significant or noteworthy revival, resurgence, or renewed prominence after a period of decline or inactivity.
-
B.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
C.
periodOfRevival
chosen
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
D.
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.
-
E.
hasModernRevival
Indicates that something has experienced a renewed interest, use, or popularity in modern times.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a4686a48190a808c86aa916ad56 |
completed | April 20, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.