Triple
T18867936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MHL |
E461488
|
entity |
| Predicate | hasPromotionPath |
P133255
|
FINISHED |
| Object | professional contracts in KHL |
—
|
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: professional contracts in KHL | Statement: [MHL, hasPromotionPath, professional contracts in KHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromotionPath Context triple: [MHL, hasPromotionPath, professional contracts in KHL]
-
A.
hasPromotionMethod
Indicates the method or strategy by which something is promoted or advertised.
-
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.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to another entity.
-
D.
hasPromotionFinal
Indicates that an entity has a promotion whose status or terms are finalized and no longer subject to change.
-
E.
hasMainPromotion
Indicates that an entity is associated with its primary or most prominent promotional offer or campaign.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.