Triple
T29804959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahora Me Llama |
E756815
|
entity |
| Predicate | boostedInternationalFameOf |
P57277
|
FINISHED |
| Object | Karol G |
—
|
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: Karol G | Statement: [Ahora Me Llama, boostedInternationalFameOf, Karol G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boostedInternationalFameOf Context triple: [Ahora Me Llama, boostedInternationalFameOf, Karol G]
-
A.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
B.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
C.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
D.
helpedPropelToMainstreamFame
chosen
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
E.
isMoreFamousThan
Indicates that one entity is better known or more widely recognized by people than 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f675295a008190a97eebccb578ce81 |
completed | May 2, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:20 p.m.