Triple
T35673116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Heavyweight Championship |
E1030778
|
entity |
| Predicate | divisionLimitUpper |
P118928
|
FINISHED |
| Object | 265 lb (120.2 kg) |
—
|
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: 265 lb (120.2 kg) | Statement: [UFC Heavyweight Championship, divisionLimitUpper, 265 lb (120.2 kg)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionLimitUpper Context triple: [UFC Heavyweight Championship, divisionLimitUpper, 265 lb (120.2 kg)]
-
A.
divisionUpperLimit
chosen
Indicates the maximum allowable value or boundary for a division operation or division-related quantity within a given context.
-
B.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
C.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
D.
innerLimit
Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
-
E.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fe2d59c8190b2845f6fb32d7a28 |
completed | May 3, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.