Triple
T31653427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Dodson |
E807795
|
entity |
| Predicate | titleChallengerFor |
P190582
|
FINISHED |
| Object | UFC Flyweight Championship |
—
|
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: UFC Flyweight Championship | Statement: [John Dodson, titleChallengerFor, UFC Flyweight Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleChallengerFor Context triple: [John Dodson, titleChallengerFor, UFC Flyweight Championship]
-
A.
challengerTitle
chosen
Indicates that an entity holds the status or designation of a challenger, typically in a competitive or contest-based context.
-
B.
titleChallengeEvent
Indicates an event in which a participant competes or acts to obtain, defend, or change a specific title or status.
-
C.
titleContenders
Indicates that the related entities are competing or in strong contention for a particular title or championship.
-
D.
challengedForTitleAgainst
Indicates that one entity competed against another in a contest or match specifically for a title or championship.
-
E.
titleHolderApprentice
Indicates that one entity holds a title or position in the capacity of an apprentice to another 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 30, 2026, 10:54 p.m.