Triple
T10622523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KOD Tour |
E250235
|
entity |
| Predicate | hasPromotionMethod |
P95022
|
FINISHED |
| Object | album-linked tour 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: album-linked tour promotion | Statement: [KOD Tour, hasPromotionMethod, album-linked tour promotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromotionMethod Context triple: [KOD Tour, hasPromotionMethod, album-linked tour promotion]
-
A.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to another entity.
-
B.
hasPromotionFrom
Indicates that an entity receives or is associated with a promotion that originates from a specified source entity (such as a campaign, organization, or person).
-
C.
hasMainPromotion
Indicates that an entity is associated with its primary or most prominent promotional offer or campaign.
-
D.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
E.
hasCoPromotionPartner
Indicates a relationship where two entities collaborate as partners to jointly promote a product, service, or initiative.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7e5074819096668b53dcc9167a |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 8:51 p.m.