Triple
T22968118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Middleweight Championship |
E571103
|
entity |
| Predicate | hasHadInterimTitles |
P150434
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [UFC Middleweight Championship, hasHadInterimTitles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHadInterimTitles Context triple: [UFC Middleweight Championship, hasHadInterimTitles, yes]
-
A.
hasInterimTitleOccasionally
Indicates that an entity temporarily holds a specific title or position on an occasional or non-continuous basis.
-
B.
hasHistoricTitles
Indicates that an entity possesses or has been associated with one or more titles, ranks, or designations of historical significance.
-
C.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
D.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
-
E.
hasPeriodTitles
Indicates that an entity is associated with one or more titles that apply specifically to a defined time period.
- F. None of above. chosen
Provenance (4 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182301f388190bb39e3d5b356dc65 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:48 p.m.