Triple
T16082290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans Continental Records |
E390138
|
entity |
| Predicate | promotionStrategy |
P37056
|
FINISHED |
| Object | heavy television promotion |
—
|
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: heavy television promotion | Statement: [Trans Continental Records, promotionStrategy, heavy television promotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionStrategy Context triple: [Trans Continental Records, promotionStrategy, heavy television promotion]
-
A.
promotionMethod
chosen
Indicates the method or channel through which something (such as a product, service, or content) is promoted or advertised.
-
B.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
-
C.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
D.
promotionTo
Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
-
E.
marketingStrategy
Indicates the approach or plan an entity uses to promote, position, and sell its products or services to a target audience.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.