Triple
T4978666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nothing Gold Can Stay |
E111828
|
entity |
| Predicate | usesContrast |
P7994
|
FINISHED |
| Object | youth and age |
—
|
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: youth and age | Statement: [Nothing Gold Can Stay, usesContrast, youth and age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesContrast Context triple: [Nothing Gold Can Stay, usesContrast, youth and age]
-
A.
createsContrastIn
Indicates a relationship where one element is used to highlight or emphasize differences with another element within a given context.
-
B.
registerContrast
Indicates that an entity records or establishes a distinction or difference between two or more items or states.
-
C.
contrastRatio
Indicates the proportional difference in luminance or intensity between two visual elements being compared.
-
D.
hasMainContrast
Indicates a primary opposing or differing relationship between two elements, highlighting the main point of contrast between them.
-
E.
themeContrast
chosen
Indicates a relationship where two themes are compared or opposed to highlight their differences or tension.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.