Triple
T30592407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East of Scotland League Cup |
E778695
|
entity |
| Predicate | hasPromotionRelevance |
P201472
|
FINISHED |
| Object | no direct 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: no direct promotion | Statement: [East of Scotland League Cup, hasPromotionRelevance, no direct promotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromotionRelevance Context triple: [East of Scotland League Cup, hasPromotionRelevance, no direct promotion]
-
A.
hasPromotionTarget
Indicates that an entity is the intended recipient, audience, or focus of a promotional activity or campaign.
-
B.
associatedWithPromotion
Indicates a relationship in which an entity is connected to, involved in, or affected by a specific promotion or promotional activity.
-
C.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to another entity.
-
D.
hasPromotionPath
Indicates that there exists a defined progression or sequence of advancement from one role, position, or level to another.
-
E.
hasPromotionMethod
Indicates the method or strategy by which something is promoted or advertised.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fff9b0338c8190a24ed0b5dc9784b2 |
completed | May 10, 2026, 3:21 a.m. |
Created at: April 29, 2026, 8:24 p.m.