Triple
T35039681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Play-Tone Records |
E1011032
|
entity |
| Predicate | hasPromotionDepartment |
P95022
|
FINISHED |
| Object | radio 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: radio promotion | Statement: [Play-Tone Records, hasPromotionDepartment, radio promotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromotionDepartment Context triple: [Play-Tone Records, hasPromotionDepartment, radio promotion]
-
A.
hasPromotionTarget
Indicates that an entity is the intended recipient, audience, or focus of a promotional activity or campaign.
-
B.
hasPromotionMethod
chosen
Indicates the method or strategy by which something is promoted or advertised.
-
C.
hasPromotionOf
Indicates that one entity grants, offers, or is associated with a promotional deal, discount, or special offer related to another entity.
-
D.
hasPromotionSystemWith
Indicates that one entity employs or is associated with a particular promotion system provided or shared by another entity.
-
E.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
Created at: May 3, 2026, 4:01 p.m.