Triple
T24978097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saúl Álvarez |
E625082
|
entity |
| Predicate | previouslyPromotedBy |
P154669
|
FINISHED |
| Object | Golden Boy Promotions |
—
|
NE NERFINISHED |
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: Golden Boy Promotions | Statement: [Saúl Álvarez, previouslyPromotedBy, Golden Boy Promotions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyPromotedBy Context triple: [Saúl Álvarez, previouslyPromotedBy, Golden Boy Promotions]
-
A.
hasBeenPromotedBy
chosen
Indicates that one entity has received a promotion as a result of the decision or action taken by another entity.
-
B.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
C.
arePromotedBy
Indicates that one entity advances in rank, position, or status as a result of an action or decision made by another entity.
-
D.
createdByPromotion
Indicates that something came into existence or was produced as a direct result of a promotion or promotional activity.
-
E.
promotedWith
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 6:02 a.m.