Triple
T33338775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarks |
E853611
|
entity |
| Predicate | increasedPopularityOf |
P156060
|
FINISHED |
| Object | Clarks Desert Boot in Jamaica |
—
|
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: Clarks Desert Boot in Jamaica | Statement: [Clarks, increasedPopularityOf, Clarks Desert Boot in Jamaica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: increasedPopularityOf Context triple: [Clarks, increasedPopularityOf, Clarks Desert Boot in Jamaica]
-
A.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
B.
achievedPopularityVia
Indicates that an entity gained recognition or widespread acceptance through a particular method, channel, or means.
-
C.
popularityResurgence
Indicates a renewed increase in attention, favor, or widespread appeal for something after a period of decline or obscurity.
-
D.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
E.
subsequentlyPopularIn
chosen
Indicates that something became popular in a particular place, group, or context after an initial point in time or after another event.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:34 a.m.