Triple
T13481019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO heavyweight title |
E318370
|
entity |
| Predicate | recognizedAsMajorTitleAlongside |
P110556
|
FINISHED |
| Object | WBA heavyweight title |
—
|
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: WBA heavyweight title | Statement: [WBO heavyweight title, recognizedAsMajorTitleAlongside, WBA heavyweight title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsMajorTitleAlongside Context triple: [WBO heavyweight title, recognizedAsMajorTitleAlongside, WBA heavyweight title]
-
A.
hasMajorTitle
Indicates that an entity holds or has been awarded a significant, high-prestige title or championship.
-
B.
recognizesTitle
Indicates that one entity acknowledges or accepts another entity’s formal title or designation as valid or appropriate.
-
C.
creditedTitle
Indicates that a particular title or role is formally attributed to an entity as a credit.
-
D.
recognizedTitleHolder
Indicates that an entity is officially acknowledged as holding a particular title or position.
-
E.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf36c6b08190ba99400600e0b662 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:42 p.m.