Triple
T38571107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimbo Slice |
E929273
|
entity |
| Predicate | madeProfessionalMMAdebutIn |
P60224
|
FINISHED |
| Object | EliteXC |
—
|
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: EliteXC | Statement: [Kimbo Slice, madeProfessionalMMAdebutIn, EliteXC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeProfessionalMMAdebutIn Context triple: [Kimbo Slice, madeProfessionalMMAdebutIn, EliteXC]
-
A.
professionalMMAStartYear
Indicates the calendar year in which an individual began competing in professional mixed martial arts.
-
B.
madeBellatorDebutIn
Indicates the event or context (such as a fight, card, or date) in which a person or fighter had their first appearance in the Bellator MMA promotion.
-
C.
madeProfessionalDebutIn
chosen
Indicates the time or event in which an individual first performed or appeared in a professional capacity within a given field or organization.
-
D.
professionalDebutDivision
Indicates the competitive division or level in which an individual first began their professional career.
-
E.
madeUFCDebutAtEvent
Indicates that an individual’s first fight or appearance in the UFC occurred at a specified event.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.