Triple
T26452643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floyd Mayweather Jr. vs. Conor McGregor |
E665394
|
entity |
| Predicate | coPromoter |
P76843
|
FINISHED |
| Object | UFC |
—
|
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: UFC | Statement: [Floyd Mayweather Jr. vs. Conor McGregor, coPromoter, UFC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coPromoter Context triple: [Floyd Mayweather Jr. vs. Conor McGregor, coPromoter, UFC]
-
A.
coSponsor
Indicates that an entity jointly supports, endorses, or backs an initiative, proposal, or activity together with one or more others.
-
B.
promotedWith
chosen
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
-
C.
laterPromoter
Indicates that one promoter occurs or becomes active at a later time than another promoter in a regulatory or temporal sequence.
-
D.
projectPromoter
Indicates that an entity is responsible for initiating, supporting, or advocating for a particular project.
-
E.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61266f0e88190aea95f89ba2bef5c |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:06 a.m.