Triple
T35526237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEVER Openweight Championship |
E1026678
|
entity |
| Predicate | weightClassRestriction |
P183392
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [NEVER Openweight Championship, weightClassRestriction, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightClassRestriction Context triple: [NEVER Openweight Championship, weightClassRestriction, none]
-
A.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
weightClassUpperLimit
Indicates the maximum allowable weight value that defines the upper boundary of a given weight class in a classification or categorization system.
-
C.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
-
D.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
E.
weightClassBelow
Indicates that one entity belongs to a lower (lighter) weight class than 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.