Triple
T25715583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver |
E644854
|
entity |
| Predicate | offersBenefitsOver |
P2188
|
FINISHED |
| Object | basic membership level |
—
|
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: basic membership level | Statement: [Silver, offersBenefitsOver, basic membership level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersBenefitsOver Context triple: [Silver, offersBenefitsOver, basic membership level]
-
A.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
B.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
C.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
D.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
E.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 9:40 p.m.