Triple
T5542730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eat Out to Help Out scheme |
E145328
|
entity |
| Predicate | discountRate |
P65289
|
FINISHED |
| Object | 50 percent |
—
|
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: 50 percent | Statement: [Eat Out to Help Out scheme, discountRate, 50 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discountRate Context triple: [Eat Out to Help Out scheme, discountRate, 50 percent]
-
A.
fareDiscount
Indicates that a reduced price is applied to a standard fare for a product or service.
-
B.
reducedCommissionRate
Indicates that the commission rate applied to a transaction or agreement is lower than the standard or previously agreed rate.
-
C.
singlePersonDiscountRate
Indicates the discount rate that applies specifically to an individual (single) person.
-
D.
offersDiscountsOn
Indicates that one entity provides price reductions or special discount deals specifically applied to another entity or its associated items or services.
-
E.
reducedDutyRateOn
Indicates a relationship where a reduced customs or tax duty rate is applied to a specified item or transaction.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc7e26481908cec8d0483170ea5 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:35 p.m.