Triple
T35673131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Heavyweight Championship |
E1030778
|
entity |
| Predicate | currentChampionWonTitleOn |
P200136
|
FINISHED |
| Object | March 4, 2023 |
—
|
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: March 4, 2023 | Statement: [UFC Heavyweight Championship, currentChampionWonTitleOn, March 4, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentChampionWonTitleOn Context triple: [UFC Heavyweight Championship, currentChampionWonTitleOn, March 4, 2023]
-
A.
currentChampionWonTitleBy
chosen
Indicates that the current champion obtained their title through the specified event, match, or method.
-
B.
championLastTitleBefore
Indicates that one entity won its most recent championship title before the time or event associated with the other entity.
-
C.
championPreviousTitleSeason
Indicates that an entity was the champion of the immediately preceding season for a given title or competition.
-
D.
defendingChampion
Indicates that an entity currently holds a title or championship and is defending it against challengers.
-
E.
championPreviousTitleYear
Indicates the year in which the current champion previously held the same title.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:05 p.m.