Triple
T11428682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Never Can Say Goodbye |
E270819
|
entity |
| Predicate | hasNotableEraOfPopularity |
P561
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Never Can Say Goodbye, hasNotableEraOfPopularity, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEraOfPopularity Context triple: [Never Can Say Goodbye, hasNotableEraOfPopularity, 1970s]
-
A.
hasEnduringPopularityOn
Indicates that something continues to be widely liked, used, or appreciated on a particular platform, medium, or context over an extended period of time.
-
B.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
C.
hasEnduringPopCulturePresence
Indicates that the subject continues to appear in, influence, or be referenced within popular culture over an extended period of time.
-
D.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
E.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c1bfb881909720c74fe0fa837f |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.