Triple
T6106654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Golf Tour |
E136132
|
entity |
| Predicate | topMoneyListEarnersReceive |
P68181
|
FINISHED |
| Object | major championship invitations |
—
|
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: major championship invitations | Statement: [Japan Golf Tour, topMoneyListEarnersReceive, major championship invitations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topMoneyListEarnersReceive Context triple: [Japan Golf Tour, topMoneyListEarnersReceive, major championship invitations]
-
A.
payingPlayers
Indicates that one or more entities are making a payment to one or more players, typically as compensation, fees, or rewards.
-
B.
careerEarningsApprox
Indicates an approximate total amount of money an entity has earned over the course of its career.
-
C.
canEarnOn
Indicates that an entity is able or permitted to receive or generate earnings from another entity, source, or activity.
-
D.
typicalAwardAmount
Indicates the usual or most common amount of an award given in this relationship.
-
E.
earnsMorePointsThan
Indicates that one entity receives a greater number of points than another entity in a given context or comparison.
- F. None of above. chosen
Provenance (4 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b806bd48190b6f020af3391adb8 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.