Triple
T35102327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBA (Super) super-middleweight title |
E1013053
|
entity |
| Predicate | rankingTier |
P37057
|
FINISHED |
| Object | Super |
—
|
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 | Statement: [WBA (Super) super-middleweight title, rankingTier, Super]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingTier Context triple: [WBA (Super) super-middleweight title, rankingTier, Super]
-
A.
rankTier
chosen
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
B.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
C.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:01 p.m.