Triple
T33338774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarks |
E853611
|
entity |
| Predicate | becameHitIn |
P155157
|
FINISHED |
| Object | Jamaica |
—
|
NE NERFINISHED |
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: Jamaica | Statement: [Clarks, becameHitIn, Jamaica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameHitIn Context triple: [Clarks, becameHitIn, Jamaica]
-
A.
becameHitDuring
Indicates that something rose in popularity or success and turned into a hit during a specified time period or event.
-
B.
wasAHitIn
chosen
Indicates that something (such as a work, product, or performance) achieved notable success or popularity within a specified context, time period, or location.
-
C.
becameBreakoutHitFor
Indicates that something achieved sudden, widespread popularity or success specifically in relation to a particular entity (such as an artist, brand, or market).
-
D.
breakthroughHitFor
Indicates that a particular work or performance served as a major breakthrough success for an entity, significantly elevating their recognition or career.
-
E.
producedHitFor
Indicates that one entity created or contributed to a successful or popular work (a "hit") for another entity.
- 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_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:34 a.m.