Triple
T13601793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Power of Yes |
E324960
|
entity |
| Predicate | promotedImage |
P110270
|
FINISHED |
| Object | customer-friendly brand image |
—
|
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: customer-friendly brand image | Statement: [The Power of Yes, promotedImage, customer-friendly brand image]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedImage Context triple: [The Power of Yes, promotedImage, customer-friendly brand image]
-
A.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
B.
promotedWith
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
-
C.
promotedService
Indicates that one entity actively markets, advertises, or otherwise promotes a particular service to others.
-
D.
publicImage
Indicates how an entity is perceived or represented by the general public or broader audience.
-
E.
promotedAt
Indicates the time or date at which an entity was elevated to a higher rank, position, or status.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07ad3f48190a2173e42c5cfedb1 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.