Triple
T30699433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican National Welterweight Championship |
E781570
|
entity |
| Predicate | weightLimitUpperBoundKg |
P26161
|
FINISHED |
| Object | 78 |
—
|
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: 78 | Statement: [Mexican National Welterweight Championship, weightLimitUpperBoundKg, 78]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightLimitUpperBoundKg Context triple: [Mexican National Welterweight Championship, weightLimitUpperBoundKg, 78]
-
A.
weightLimitInKilograms
chosen
Indicates the maximum allowable weight for something, expressed in kilograms.
-
B.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
-
C.
weightLimitLowerBoundKg
Indicates the minimum allowable weight, in kilograms, that satisfies a specified limit or constraint.
-
D.
hasUpperDeadweightLimit
Indicates that there is a specified maximum deadweight capacity or load limit applicable to an entity.
-
E.
hasVehicleWeightLimit
Indicates that there is a maximum allowable weight for vehicles associated with, or permitted to use, a given object or location.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:34 p.m.