Triple
T26489234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO super featherweight title |
E664909
|
entity |
| Predicate | requiresTitleDefenses |
P180393
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WBO super featherweight title, requiresTitleDefenses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTitleDefenses Context triple: [WBO super featherweight title, requiresTitleDefenses, yes]
-
A.
isTitleDefenseFor
Indicates that an event, match, or competition serves as the defending champion’s attempt to retain an existing title or championship.
-
B.
requiresForDefense
Indicates that one entity must have or obtain another entity as a necessary condition to provide or maintain defense.
-
C.
requiresTitle
Indicates that something cannot proceed or be considered valid unless a specific title has been provided or assigned.
-
D.
providesDefence
Indicates that one entity offers protection or defensive support to another entity.
-
E.
titleDefendedBy
Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 27, 2026, 12:32 a.m.