Triple
T24944471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | super welterweight |
E624148
|
entity |
| Predicate | adjacentHigherClass |
P3584
|
FINISHED |
| Object | 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: middleweight | Statement: [super welterweight, adjacentHigherClass, middleweight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentHigherClass Context triple: [super welterweight, adjacentHigherClass, middleweight]
-
A.
hasHigherClass
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
B.
nextHigherRank
chosen
Indicates that one entity holds the immediately superior rank or level in a hierarchy relative to another entity.
-
C.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
D.
higherClassificationInArea
Indicates that one entity is classified at a higher taxonomic or categorical level than another within a specified area or context.
-
E.
adjacentLine
Indicates that one line is directly next to another line, sharing a common boundary or position without overlapping.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:53 a.m.