Triple
T16261767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC heavyweight division |
E394770
|
entity |
| Predicate | hasInterimTitleOccasionally |
P122409
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UFC heavyweight division, hasInterimTitleOccasionally, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterimTitleOccasionally Context triple: [UFC heavyweight division, hasInterimTitleOccasionally, true]
-
A.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
B.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
-
C.
isTitledAfter
Indicates that one entity has been given a name or title derived from, in honor of, or referencing another entity.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
mayBeTitled
Indicates that an entity can optionally bear or be assigned a particular title, but is not required to have it.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c4a0b08190af3574f087205afc |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.