Triple
T6107201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 1 |
E136144
|
entity |
| Predicate | finalSubmissionType |
P68190
|
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 1, finalSubmissionType, rear-naked choke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSubmissionType Context triple: [UFC 1, finalSubmissionType, rear-naked choke]
-
A.
submissionType
Indicates the specific category or format under which something is submitted (e.g., as a document, assignment, application, or other submission class).
-
B.
finalReportType
Indicates the specific category or format assigned to a report when it is in its final, completed state.
-
C.
submissionTypes
Indicates the categories or formats in which something can be submitted or has been submitted within a given context.
-
D.
finalPassing
Indicates that an entity successfully completes or passes a final evaluation, test, or stage in a process.
-
E.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b806bd48190b6f020af3391adb8 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.