Triple
T4424624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honey browser extension |
E95179
|
entity |
| Predicate | userBenefit |
P487
|
FINISHED |
| Object | saves money on online purchases |
—
|
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: saves money on online purchases | Statement: [Honey browser extension, userBenefit, saves money on online purchases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userBenefit Context triple: [Honey browser extension, userBenefit, saves money on online purchases]
-
A.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
benefits
chosen
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
C.
exclusiveBenefit
Indicates that a benefit is provided to one party or group in a way that excludes others from receiving the same advantage.
-
D.
primaryBenefit
Indicates that one entity serves as the main or most important advantage, gain, or positive outcome associated with another entity.
-
E.
benefitsState
Indicates that one entity provides an advantage, improvement, or positive outcome to a state or governmental entity.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554ca5208190ba2661616dcf071c |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.