Triple
T33929143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBF bantamweight title |
E869836
|
entity |
| Predicate | requiresMandatoryDefences |
P180393
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [IBF bantamweight title, requiresMandatoryDefences, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMandatoryDefences Context triple: [IBF bantamweight title, requiresMandatoryDefences, true]
-
A.
requiresForDefense
Indicates that one entity must have or obtain another entity as a necessary condition to provide or maintain defense.
-
B.
requiresTitleDefenses
chosen
Indicates that holding or obtaining a particular title is contingent on successfully completing specified title defense events or matches.
-
C.
providesDefence
Indicates that one entity offers protection or defensive support to another entity.
-
D.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
E.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 1, 2026, 1:49 a.m.