Triple
T37759314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Trigg |
E941212
|
entity |
| Predicate | titleChallengerInOrganization |
P144477
|
FINISHED |
| Object | Ultimate Fighting 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: Ultimate Fighting Championship | Statement: [Frank Trigg, titleChallengerInOrganization, Ultimate Fighting Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleChallengerInOrganization Context triple: [Frank Trigg, titleChallengerInOrganization, Ultimate Fighting Championship]
-
A.
challengerTitle
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.
titleHolderApprentice
Indicates that one entity holds a title or position in the capacity of an apprentice to another entity.
-
D.
challengerStatus
chosen
Indicates the role or condition of an entity as a challenger in a competitive or adversarial context.
-
E.
titleChallengeLocation
Indicates the location where a title-related challenge or contest takes place.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:19 p.m.