Triple
T35673134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Heavyweight Championship |
E1030778
|
entity |
| Predicate | formerChampion |
P28766
|
FINISHED |
| Object | Mark Coleman |
—
|
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: Mark Coleman | Statement: [UFC Heavyweight Championship, formerChampion, Mark Coleman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerChampion Context triple: [UFC Heavyweight Championship, formerChampion, Mark Coleman]
-
A.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
B.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
-
C.
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.
-
D.
notableFormerChampion
chosen
Indicates that an entity was once a champion of something and is recognized as particularly distinguished or prominent in that former champion role.
-
E.
formerChampionTeam
Indicates that a team once held a championship title in the relevant competition or league but no longer does.
- 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_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 3, 2026, 4:05 p.m.