Triple
T14336270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CM Punk |
E355473
|
entity |
| Predicate | MMARecordOfficial |
P110496
|
FINISHED |
| Object | 0–1 (1 no contest) |
—
|
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: 0–1 (1 no contest) | Statement: [CM Punk, MMARecordOfficial, 0–1 (1 no contest)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MMARecordOfficial Context triple: [CM Punk, MMARecordOfficial, 0–1 (1 no contest)]
-
A.
MMAOrganization
Indicates an organizational relationship where an entity functions as a mixed martial arts promotion or governing body associated with fighters, events, or titles.
-
B.
professionalMMARecordLosses
chosen
Indicates the number of losses an entity has in their professional mixed martial arts competition record.
-
C.
professionalMMAStartYear
Indicates the calendar year in which an individual began competing in professional mixed martial arts.
-
D.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling context.
-
E.
boxingRecordSummary
Indicates the summarized outcome or performance record of an entity in boxing matches, such as total wins, losses, and related statistics.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c2241e48190a0c626b3d741966a |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.