Triple
T25219773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO light welterweight title |
E631928
|
entity |
| Predicate | sanctioningFeePayer |
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: [WBO light welterweight title, sanctioningFeePayer, promoter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctioningFeePayer Context triple: [WBO light welterweight title, sanctioningFeePayer, promoter]
-
A.
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.
-
B.
paymasterGeneral
Indicates a relationship where one entity serves as the chief official responsible for authorizing or overseeing payments on behalf of another entity or organization.
-
C.
sanctioningStatus
Indicates the current status of formal penalties, restrictions, or sanctions applied to an entity by an authority.
-
D.
paidBy
chosen
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
E.
sanctionedAs
Indicates that an entity is officially approved, authorized, or recognized in a particular role, status, or capacity by a relevant authority.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:02 p.m.