Triple
T17729510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superstrat guitars |
E442549
|
entity |
| Predicate | historicalPopularityPeak |
P105129
|
FINISHED |
| Object | 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: 1980s | Statement: [Superstrat guitars, historicalPopularityPeak, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPopularityPeak Context triple: [Superstrat guitars, historicalPopularityPeak, 1980s]
-
A.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
B.
notablePopularityPeriod
chosen
Indicates the time span during which something was especially popular or widely recognized.
-
C.
peakedWithinTopTenOn
Indicates that something (such as a work, product, or performance) reached a highest ranking position within the top ten on a specified chart, list, or ranking system.
-
D.
historicallyPopularIn
Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
-
E.
famePeak
Indicates the time or point at which an entity reaches its highest level of fame or public recognition.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e5ba7c81908f8b06eb6859067f |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.