Triple
T17492424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'll Feel a Whole Lot Better |
E425956
|
entity |
| Predicate | isEnduringStandardOf |
P34280
|
FINISHED |
| Object | 1960s folk rock |
—
|
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: 1960s folk rock | Statement: [I'll Feel a Whole Lot Better, isEnduringStandardOf, 1960s folk rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEnduringStandardOf Context triple: [I'll Feel a Whole Lot Better, isEnduringStandardOf, 1960s folk rock]
-
A.
isStandardOf
chosen
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
B.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
C.
isStandardOn
Indicates that a particular feature, option, or component is included by default as part of another item, rather than being optional or extra.
-
D.
isPartOfStandard
Indicates that something belongs to, is included within, or conforms to a defined standard or standardized set.
-
E.
jointStandardOf
Indicates that two or more entities share responsibility for defining, maintaining, or adhering to the same standard or set of rules.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d6bd548190b4c6fae27c2a9ae8 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.