Triple
T34819985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 267 |
E1003742
|
entity |
| Predicate | coMainEventDecisionType |
P181899
|
FINISHED |
| Object | unanimous decision |
—
|
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: unanimous decision | Statement: [UFC 267, coMainEventDecisionType, unanimous decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coMainEventDecisionType Context triple: [UFC 267, coMainEventDecisionType, unanimous decision]
-
A.
mainEventDecision
Indicates a decision or choice that determines the primary outcome or direction of the 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.
canMainEvent
Indicates that an entity is capable of serving as the primary or central event within a larger event structure or scenario.
-
D.
coMainEventWinner
Indicates that an entity is one of the winners of a shared or jointly headlined main event.
-
E.
coMainEventBoutType
Indicates the type or category of the bout designated as the co-main event within a combat sports or similar event card.
- 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_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4 p.m.