Triple
T23684582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 239 |
E585127
|
entity |
| Predicate | promotionTagline |
P113853
|
FINISHED |
| Object | Jones vs. Santos |
—
|
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: Jones vs. Santos | Statement: [UFC 239, promotionTagline, Jones vs. Santos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionTagline Context triple: [UFC 239, promotionTagline, Jones vs. Santos]
-
A.
promotionBy
Indicates that one entity advances, elevates, or publicizes another entity, typically by increasing its status, visibility, or level.
-
B.
taglineMatch
chosen
Indicates that two entities share the same tagline or that a tagline corresponds to a given entity.
-
C.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
D.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
-
E.
promotionGimmick
Indicates a relationship where something is used as a special tactic or device to attract attention or boost interest in a promotion.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4fb26c88190a6776e4dfd10d54c |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.