Triple
T22058268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBC middleweight title |
E545079
|
entity |
| Predicate | rankingInfluence |
P23822
|
FINISHED |
| Object | influences global middleweight rankings |
—
|
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: influences global middleweight rankings | Statement: [WBC middleweight title, rankingInfluence, influences global middleweight rankings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingInfluence Context triple: [WBC middleweight title, rankingInfluence, influences global middleweight rankings]
-
A.
rankingImpact
chosen
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
B.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
C.
relatedRanking
Indicates a relationship where one item’s ranking is connected to or influenced by another item’s ranking.
-
D.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
E.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285959f48190b89527b3f9e7ab11 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.