Triple
T28461195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga Premier de México |
E720157
|
entity |
| Predicate | hasPromotionFunction |
P198256
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Liga Premier de México, hasPromotionFunction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPromotionFunction Context triple: [Liga Premier de México, hasPromotionFunction, true]
-
A.
hasPromotionMethod
Indicates the method or strategy by which something is promoted or advertised.
-
B.
hasPromotionMechanism
Indicates that there exists a specific method, strategy, or process by which something is promoted, advanced, or made more widely known.
-
C.
hasPromotionTarget
Indicates that an entity is the intended recipient, audience, or focus of a promotional activity or campaign.
-
D.
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).
-
E.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to another entity.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
| PDg | Predicate description generation | batch_69fed6d90f2081909cd21e5e973a6b89 |
completed | May 9, 2026, 6:40 a.m. |
Created at: April 28, 2026, 2:40 a.m.