Triple
T31358284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Bachata |
E799795
|
entity |
| Predicate | isMarketingLabelFor |
P171270
|
FINISHED |
| Object | Romeo Santos |
—
|
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: Romeo Santos | Statement: [King of Bachata, isMarketingLabelFor, Romeo Santos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMarketingLabelFor Context triple: [King of Bachata, isMarketingLabelFor, Romeo Santos]
-
A.
isMarketingRelated
Indicates that something is associated with, pertains to, or is relevant to marketing activities, strategies, or objectives.
-
B.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
C.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
-
D.
hasMarketingElement
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
E.
hasMarketingDescription
Indicates that an entity is associated with a textual marketing-oriented description used to promote or present it.
- F. None of above. chosen
Provenance (4 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f4900b88190872299a7ec7e7674 |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:17 p.m.