Triple
T13212735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 81 |
E314533
|
entity |
| Predicate | methodMainEvent |
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 81, methodMainEvent, submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodMainEvent Context triple: [UFC 81, methodMainEvent, submission]
-
A.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
B.
mainEvents
Indicates that the referenced entities are the primary or most significant events within a given context, sequence, or narrative.
-
C.
mainEntranceOn
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
-
D.
numberOfMainEvents
Indicates the total count of primary or most significant events associated with a given entity or context.
-
E.
mainEventStipulation
Indicates that a specified condition, requirement, or rule must be satisfied for the main event or primary occurrence in a given context.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9f0f148190a0698ef27573c885 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:17 p.m.