Triple
T34804053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 257 |
E1003299
|
entity |
| Predicate | resultCoMainEventMethod |
P181899
|
FINISHED |
| Object | TKO |
—
|
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: TKO | Statement: [UFC 257, resultCoMainEventMethod, TKO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultCoMainEventMethod Context triple: [UFC 257, resultCoMainEventMethod, TKO]
-
A.
coMainEventMethod
Indicates that an entity serves as a primary or principal method used to carry out or realize a main event.
-
B.
coMainEvent
Indicates that two or more events share equal primary status as the main featured events within the same program or occasion.
-
C.
mainEventResult
Indicates the outcome or consequence that directly results from the primary event in a given context.
-
D.
coMainEventDecisionType
chosen
Indicates the type or outcome of the decision rendered in a co-main event (e.g., how the result of that shared main contest was determined).
-
E.
methodMainEvent
Indicates that an event is the primary or main event associated with a particular method.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 3:59 p.m.