Triple
T35679630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 82 |
E1030967
|
entity |
| Predicate | submissionOfTheNightWinner |
P154920
|
FINISHED |
| Object | Anderson Silva |
—
|
NE NERFINISHED |
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: Anderson Silva | Statement: [UFC 82, submissionOfTheNightWinner, Anderson Silva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submissionOfTheNightWinner Context triple: [UFC 82, submissionOfTheNightWinner, Anderson Silva]
-
A.
hasSubmissionOfTheNightAwards
chosen
Indicates that an entity has received one or more "Submission of the Night" awards.
-
B.
submissionDecidesWinner
Indicates that the outcome or winner of a contest, match, or decision process is determined by a submission made by a participant.
-
C.
submitsNominationsTo
Indicates that one party formally sends or presents nominations to another party for consideration or approval.
-
D.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
E.
submissionWith
Indicates that one entity is submitted together with, or as part of the same submission as, another entity.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fe8ce1481908c66234d2be16d9d |
completed | May 3, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.