Triple
T10329482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Storage API |
E242839
|
entity |
| Predicate | supportsPersistenceType |
P11254
|
FINISHED |
| Object | persistent storage via localStorage |
—
|
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: persistent storage via localStorage | Statement: [Web Storage API, supportsPersistenceType, persistent storage via localStorage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPersistenceType Context triple: [Web Storage API, supportsPersistenceType, persistent storage via localStorage]
-
A.
supportsPersistence
Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
-
B.
persistsAfter
Indicates that one state, condition, or effect continues to exist after a specified event, time point, or other state has occurred or ended.
-
C.
persistence
Indicates a continued or repeated existence, occurrence, or effort of something over time despite potential changes or obstacles.
-
D.
persistenceModel
Indicates that one entity serves as the persistence representation or storage model used to save, load, or otherwise persist the state of another entity.
-
E.
supportsDatastoreType
chosen
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
- 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_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. |
Created at: April 6, 2026, 11:52 a.m.