Triple
T36153083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC featherweight division |
E1045646
|
entity |
| Predicate | lowerWeightBound |
P171307
|
FINISHED |
| Object | over 135 pounds |
—
|
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: over 135 pounds | Statement: [UFC featherweight division, lowerWeightBound, over 135 pounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerWeightBound Context triple: [UFC featherweight division, lowerWeightBound, over 135 pounds]
-
A.
lowerBoundProperty
Indicates that one entity serves as the minimum or lowest permissible value, limit, or constraint for another entity or quantity.
-
B.
weightLimitLowerBoundLb
chosen
Indicates the minimum allowable weight, expressed in pounds, that satisfies a specified limit or constraint.
-
C.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
D.
lowerBoundGrowth
Indicates that one quantity grows at least as fast as another, establishing a minimum rate or bound on its growth relative to that reference.
-
E.
lowerBoundaryLocation
Indicates the place or region where the lower or bottom boundary of something is situated.
- 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_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.