Triple
T22947817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | It’s a Living |
E569921
|
entity |
| Predicate | revivalOrSyndicatedRunPeriod |
P48377
|
FINISHED |
| Object | mid to late 1980s |
—
|
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: mid to late 1980s | Statement: [It’s a Living, revivalOrSyndicatedRunPeriod, mid to late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalOrSyndicatedRunPeriod Context triple: [It’s a Living, revivalOrSyndicatedRunPeriod, mid to late 1980s]
-
A.
revivalEndTime
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
B.
revivalRunStart
Indicates the point in time or event at which a revival process or renewed operation begins.
-
C.
periodOfRevival
chosen
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
D.
revivalNumberOfSeries
Indicates the ordinal position of a particular revival within the overall sequence of revivals of a series.
-
E.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819fbf8c8190ad80c93f1507aa73 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.