Triple
T16651112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Under the Iron Sea Tour |
E404603
|
entity |
| Predicate | hasPromotionalPurpose |
P61924
|
FINISHED |
| Object | promote the album Under the Iron Sea |
—
|
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: promote the album Under the Iron Sea | Statement: [Under the Iron Sea Tour, hasPromotionalPurpose, promote the album Under the Iron Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromotionalPurpose Context triple: [Under the Iron Sea Tour, hasPromotionalPurpose, promote the album Under the Iron Sea]
-
A.
hasMainPromotion
Indicates that an entity is associated with its primary or most prominent promotional offer or campaign.
-
B.
hasPromotionalSingle
Indicates that an entity has an associated promotional single released to market or media for promotional purposes.
-
C.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
D.
promotionalFor
chosen
Indicates that one entity serves to advertise, market, or otherwise promote another entity, such as a product, service, event, or brand.
-
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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf6cfc481909b183348c407e046 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.