Triple
T34819976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 267 |
E1003742
|
entity |
| Predicate | mainEventSubmissionType |
P182880
|
FINISHED |
| Object | rear-naked choke |
—
|
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: rear-naked choke | Statement: [UFC 267, mainEventSubmissionType, rear-naked choke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventSubmissionType Context triple: [UFC 267, mainEventSubmissionType, rear-naked choke]
-
A.
submissionTypeCoMainEvent
Indicates that the submission is classified as a co-main event within an event or program hierarchy.
-
B.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
C.
mainEventDecision
Indicates a decision or choice that determines the primary outcome or direction of the main event.
-
D.
submissionHoldMainEvent
Indicates that a submission action causes the primary or main event to be placed on hold or temporarily paused.
-
E.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f794f24e588190965e39b77534d53f |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4 p.m.