Triple
T10329476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Storage API |
E242839
|
entity |
| Predicate | advantageOverCookies |
P93444
|
FINISHED |
| Object | larger storage capacity |
—
|
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: larger storage capacity | Statement: [Web Storage API, advantageOverCookies, larger storage capacity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advantageOverCookies Context triple: [Web Storage API, advantageOverCookies, larger storage capacity]
-
A.
advantageOverPasswords
Indicates that one method, system, or approach provides benefits or improvements compared to traditional password-based authentication.
-
B.
advantageOverHMAC
Indicates that one method, system, or approach provides a security or performance benefit compared to using HMAC.
-
C.
advantageOverHDD
Indicates that one entity possesses a benefit, superiority, or improvement when compared to a hard disk drive (HDD).
-
D.
notableAdvantage
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
E.
siteAdvantage
Indicates that one entity benefits from a favorable or superior position, condition, or context relative to another entity.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.