Triple
T38415150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Gustafsson |
E901581
|
entity |
| Predicate | titleChallengerAgainst |
P138948
|
FINISHED |
| Object | Jon Jones |
—
|
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: Jon Jones | Statement: [Alexander Gustafsson, titleChallengerAgainst, Jon Jones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleChallengerAgainst Context triple: [Alexander Gustafsson, titleChallengerAgainst, Jon Jones]
-
A.
challengerTitle
Indicates that an entity holds the status or designation of a challenger, typically in a competitive or contest-based context.
-
B.
challengedForTitleAgainst
chosen
Indicates that one entity competed against another in a contest or match specifically for a title or championship.
-
C.
featuredChallenger
Indicates that an entity is highlighted or designated as a primary or special challenger in a given context or competition.
-
D.
titleChallengeEvent
Indicates an event in which a participant competes or acts to obtain, defend, or change a specific title or status.
-
E.
opponentTitle
Indicates that the object is the formal title or designation held by an opponent in a competitive or adversarial context.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 3, 2026, 4:31 p.m.