Triple
T16261751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC heavyweight division |
E394770
|
entity |
| Predicate | championAsOf |
P108809
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [UFC heavyweight division, championAsOf, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championAsOf Context triple: [UFC heavyweight division, championAsOf, 2024]
-
A.
isChampionAtTimeOf
chosen
Indicates that an entity holds the status or title of champion at a specified point in time.
-
B.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
C.
mostRecentChampion
Indicates that the subject is the entity that most recently won a particular competition, title, or championship.
-
D.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
-
E.
championManager
Indicates that one entity serves as the manager, coach, or primary overseer responsible for the success or performance of a champion entity.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c4a0b08190af3574f087205afc |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.