Triple
T23742270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPMG Women’s PGA Championship |
E586706
|
entity |
| Predicate | co-sanctionedBy |
P152377
|
FINISHED |
| Object | LPGA Tour |
—
|
NE NERFINISHED |
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: LPGA Tour | Statement: [KPMG Women’s PGA Championship, co-sanctionedBy, LPGA Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: co-sanctionedBy Context triple: [KPMG Women’s PGA Championship, co-sanctionedBy, LPGA Tour]
-
A.
coSanctionedBy
chosen
Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
-
B.
coSanctionedWith
Indicates that an entity is subject to sanctions together with another entity, typically as part of the same sanctioning action or regime.
-
C.
sanctionedAs
Indicates that an entity is officially approved, authorized, or recognized in a particular role, status, or capacity by a relevant authority.
-
D.
sanction
Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
-
E.
notSanctionedBy
Indicates that an action, entity, or event is explicitly not approved, authorized, or endorsed by the referenced authority or organization.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad734b08190a4b3365df97c73e1 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.