Triple
T34819975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 267 |
E1003742
|
entity |
| Predicate | mainEventMethod |
P108540
|
FINISHED |
| Object | submission |
—
|
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: submission | Statement: [UFC 267, mainEventMethod, submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEventMethod Context triple: [UFC 267, mainEventMethod, submission]
-
A.
methodMainEvent
chosen
Indicates that an event is the primary or main event associated with a particular method.
-
B.
mainEventClass
Indicates that an event is classified as the primary or most central event within a given context or dataset.
-
C.
mainEventManager
Indicates that an entity serves as the primary controller or coordinator responsible for managing a central event or set of events in relation to another entity.
-
D.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
E.
mainEventResult
Indicates the outcome or consequence that directly results from the primary event in a given context.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.