Triple
T17977557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | troll dolls |
E449515
|
entity |
| Predicate | hadPopularityResurgenceIn |
P100682
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [troll dolls, hadPopularityResurgenceIn, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPopularityResurgenceIn Context triple: [troll dolls, hadPopularityResurgenceIn, 1990s]
-
A.
popularityResurgence
Indicates a renewed increase in attention, favor, or widespread appeal for something after a period of decline or obscurity.
-
B.
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.
-
C.
helpedPropelToMainstreamFame
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
D.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
E.
revivedInDecade
chosen
Indicates that an entity was brought back into use, popularity, or active existence during a specified decade.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b200e9108190bcdde5ba7938ba94 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.