Triple
T12467551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBC light heavyweight title |
E297964
|
entity |
| Predicate | weightRangeLowerBound |
P17139
|
FINISHED |
| Object | 168 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: 168 pounds | Statement: [WBC light heavyweight title, weightRangeLowerBound, 168 pounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightRangeLowerBound Context triple: [WBC light heavyweight title, weightRangeLowerBound, 168 pounds]
-
A.
weightRangeDescription
Indicates the textual description that specifies the range within which an entity’s weight falls.
-
B.
lowerLimit
chosen
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
C.
lowerLimitVariesBy
Indicates that the lower limit of a quantity or range changes depending on, or is determined by, another variable or condition.
-
D.
minimumMass
Indicates the smallest mass value that an entity or system is required, allowed, or observed to have within a given context.
-
E.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.