Triple
T13041253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSI 5* |
E327195
|
entity |
| Predicate | minimumPrizeMoneyRequirement |
P53002
|
FINISHED |
| Object | subject to FEI minimum prize money thresholds |
—
|
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: subject to FEI minimum prize money thresholds | Statement: [CSI 5*, minimumPrizeMoneyRequirement, subject to FEI minimum prize money thresholds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumPrizeMoneyRequirement Context triple: [CSI 5*, minimumPrizeMoneyRequirement, subject to FEI minimum prize money thresholds]
-
A.
prizeMoneyLevel
Indicates the relative amount or tier of monetary reward associated with a prize or award.
-
B.
hasPrizeMoney
Indicates that an entity awards, offers, or is associated with a specified amount of prize money.
-
C.
prizeMoneyCurrency
Indicates the currency in which the prize money is denominated or paid.
-
D.
minimumPayoutThreshold
chosen
Indicates the lowest payout amount or value that must be reached before a payment or disbursement is triggered.
-
E.
equalPrizeMoneySince
Indicates that the prize money awarded has been the same for the referenced parties starting from a specific point in time.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:56 p.m.