Triple
T24021717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat Miletich |
E594840
|
entity |
| Predicate | titleDefense |
P83086
|
FINISHED |
| Object | defended UFC welterweight title multiple times |
—
|
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: defended UFC welterweight title multiple times | Statement: [Pat Miletich, titleDefense, defended UFC welterweight title multiple times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleDefense Context triple: [Pat Miletich, titleDefense, defended UFC welterweight title multiple times]
-
A.
isTitleDefenseFor
Indicates that an event, match, or competition serves as the defending champion’s attempt to retain an existing title or championship.
-
B.
titleDefendedBy
chosen
Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
-
C.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
E.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d7667ff08190bfd14aa4eb776f21 |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:50 p.m.