Triple
T35805457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruiserweight division on SmackDown |
E1035090
|
entity |
| Predicate | targetWeightClass |
P183392
|
FINISHED |
| Object | lighter wrestlers |
—
|
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: lighter wrestlers | Statement: [Cruiserweight division on SmackDown, targetWeightClass, lighter wrestlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetWeightClass Context triple: [Cruiserweight division on SmackDown, targetWeightClass, lighter wrestlers]
-
A.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
-
C.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
-
D.
competesInWeightClass
Indicates that an entity participates in a competition within a specific weight classification or division.
-
E.
weightClassRestriction
chosen
Indicates that an action or relationship is limited or governed by specified weight categories or thresholds.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 3, 2026, 4:06 p.m.