Triple
T26489251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO super featherweight title |
E664909
|
entity |
| Predicate | enforcesWeightLimitAtWeighIn |
P161016
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WBO super featherweight title, enforcesWeightLimitAtWeighIn, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesWeightLimitAtWeighIn Context triple: [WBO super featherweight title, enforcesWeightLimitAtWeighIn, yes]
-
A.
requiresWeighIn
Indicates that one entity must provide an opinion, decision, or input before another entity’s action or process can proceed.
-
B.
hasVehicleWeightLimit
Indicates that there is a maximum allowable weight for vehicles associated with, or permitted to use, a given object or location.
-
C.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
-
D.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
-
E.
greatWeightAppliesTo
Indicates that a condition, rule, or influence of great weight or importance is applied to a particular entity or case.
- F. None of above. chosen
Provenance (4 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61302356c8190b8dc90949fdff41b |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 12:32 a.m.