Triple
T30321024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leon Spinks |
E771198
|
entity |
| Predicate | boxingWeightClass |
P8068
|
FINISHED |
| Object | heavyweight |
—
|
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: heavyweight | Statement: [Leon Spinks, boxingWeightClass, heavyweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boxingWeightClass Context triple: [Leon Spinks, boxingWeightClass, heavyweight]
-
A.
weightClass
chosen
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
-
C.
launchWeightClass
Indicates the weight category or class into which a launch (typically of a vehicle, payload, or mission) is classified based on its mass.
-
D.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
-
E.
weightClassOrder
Indicates the relative ranking or sequence of entities based on their weight class, from lighter to heavier (or vice versa).
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68197aac481909b701a91af7406e5 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:52 p.m.