Triple
T24274704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBA light middleweight title |
E605374
|
entity |
| Predicate | divisionAlsoKnownAs |
P155629
|
FINISHED |
| Object | super welterweight |
—
|
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: super welterweight | Statement: [WBA light middleweight title, divisionAlsoKnownAs, super welterweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionAlsoKnownAs Context triple: [WBA light middleweight title, divisionAlsoKnownAs, super welterweight]
-
A.
divisionRenamedFrom
Indicates that a division currently known by one name was previously known by another specified name.
-
B.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
C.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
D.
divisionRenamedTo
Indicates that an organizational division has changed its name to a new specified name.
-
E.
divisionFormedFrom
Indicates that an organizational division was created by splitting off from or being reorganized out of another existing 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5da53c8190810f4e7777d112ba |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:07 a.m.