Triple
T24944486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | super welterweight |
E624148
|
entity |
| Predicate | typicalFighterWeight |
P178990
|
FINISHED |
| Object | around 154 pounds |
—
|
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: around 154 pounds | Statement: [super welterweight, typicalFighterWeight, around 154 pounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFighterWeight Context triple: [super welterweight, typicalFighterWeight, around 154 pounds]
-
A.
launchWeightClass
Indicates the weight category or class into which a launch (typically of a vehicle, payload, or mission) is classified based on its mass.
-
B.
weightClass
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
C.
typicalAircraftStrength
Indicates the usual or characteristic level of military strength or capability associated with an aircraft.
-
D.
emptyWeight
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
E.
fighter1Reach
Indicates the arm length or striking distance available to the first fighter in a comparison or matchup.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 18, 2026, 5:53 a.m.