Triple
T35673123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Heavyweight Championship |
E1030778
|
entity |
| Predicate | firstChampionCrownedAt |
P6585
|
FINISHED |
| Object | UFC 12 |
E1588221
|
NE 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: UFC 12 | Statement: [UFC Heavyweight Championship, firstChampionCrownedAt, UFC 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstChampionCrownedAt Context triple: [UFC Heavyweight Championship, firstChampionCrownedAt, UFC 12]
-
A.
firstTimeChampion
Indicates that an entity has won a championship title for the first time in its history.
-
B.
isChampionAtTimeOf
Indicates that an entity holds the status or title of champion at a specified point in time.
-
C.
firstWinnerYear
Indicates the year in which an entity first won a particular competition, award, or title.
-
D.
officialChampionDesignationYear
Indicates the year in which an entity was formally designated or recognized as a champion.
-
E.
firstChampion
chosen
Indicates that one entity is the earliest or original champion or title-holder in relation to another entity.
- F. None of above.
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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d0476c88190982bad0ca9b3c084 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.