Triple
T24274693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBA light middleweight title |
E605374
|
entity |
| Predicate | sanctionFeePaidBy |
P12961
|
FINISHED |
| Object | promoter |
—
|
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: promoter | Statement: [WBA light middleweight title, sanctionFeePaidBy, promoter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctionFeePaidBy Context triple: [WBA light middleweight title, sanctionFeePaidBy, promoter]
-
A.
paidBy
chosen
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
B.
previouslyPaidTo
Indicates that a payment was made in the past from one entity to another.
-
C.
sanctionedAs
Indicates that an entity is officially approved, authorized, or recognized in a particular role, status, or capacity by a relevant authority.
-
D.
isFeePaying
Indicates that an entity is required to pay a fee in order to participate in, access, or receive a specified service, resource, or activity.
-
E.
coSanctionedBy
Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5da53c8190810f4e7777d112ba |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.