Triple
T36153107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC featherweight division |
E1045646
|
entity |
| Predicate | hasWeightClassCode |
P8068
|
FINISHED |
| Object | 145 lb |
—
|
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: 145 lb | Statement: [UFC featherweight division, hasWeightClassCode, 145 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeightClassCode Context triple: [UFC featherweight division, hasWeightClassCode, 145 lb]
-
A.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
B.
weightClass
chosen
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
C.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
-
D.
competesInWeightClass
Indicates that an entity participates in a competition within a specific weight classification or division.
-
E.
weightClassRestriction
Indicates that an action or relationship is limited or governed by specified weight categories or thresholds.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.