Triple
T24944473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | super welterweight |
E624148
|
entity |
| Predicate | standardUpperLimit |
P118928
|
FINISHED |
| Object | 69.9 kilograms |
—
|
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: 69.9 kilograms | Statement: [super welterweight, standardUpperLimit, 69.9 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardUpperLimit Context triple: [super welterweight, standardUpperLimit, 69.9 kilograms]
-
A.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
B.
baselineLimit
Indicates a threshold or maximum baseline level that something is not expected or allowed to exceed.
-
C.
divisionUpperLimit
chosen
Indicates the maximum allowable value or boundary for a division operation or division-related quantity within a given context.
-
D.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
E.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:53 a.m.