Triple
T10329509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Storage API |
E242839
|
entity |
| Predicate | canBeClearedBy |
P2359
|
FINISHED |
| Object | user clearing site data |
—
|
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: user clearing site data | Statement: [Web Storage API, canBeClearedBy, user clearing site data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeClearedBy Context triple: [Web Storage API, canBeClearedBy, user clearing site data]
-
A.
canBeRemovedBy
chosen
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
B.
clearingSystem
Indicates that one entity functions as the financial clearing mechanism or infrastructure used to settle transactions for another entity.
-
C.
canBeLostBy
Indicates that something is capable of being lost or forfeited by a particular entity.
-
D.
clearingHouse
Indicates that an entity functions as an intermediary organization that receives, processes, and redistributes transactions, information, or obligations between other parties.
-
E.
canDestroy
Indicates that one entity has the ability or power to destroy 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_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.