Triple
T32166688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinny Pazienza |
E821600
|
entity |
| Predicate | foughtAfterInjuryAtWeightClass |
P173656
|
FINISHED |
| Object | super middleweight |
—
|
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: super middleweight | Statement: [Vinny Pazienza, foughtAfterInjuryAtWeightClass, super middleweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtAfterInjuryAtWeightClass Context triple: [Vinny Pazienza, foughtAfterInjuryAtWeightClass, super middleweight]
-
A.
foughtAfter
Indicates that one entity engaged in a fight or battle after another entity had already fought.
-
B.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
C.
performedByWeightClass
Indicates that an action or event is carried out by an entity belonging to a specific weight class.
-
D.
laterFightsFor
Indicates that one entity fights on behalf of or in support of another entity at a later time than some referenced point or event.
-
E.
secondBoutWeightClass
Indicates the weight class in which an entity competes or participates during its second bout or match.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba2089588190808706cc40fea7d6 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:33 a.m.