Triple
T33436061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP cookie |
E856240
|
entity |
| Predicate | canBeDeletedBy |
P2359
|
FINISHED |
| Object | user via browser controls |
—
|
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 via browser controls | Statement: [HTTP cookie, canBeDeletedBy, user via browser controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDeletedBy Context triple: [HTTP cookie, canBeDeletedBy, user via browser controls]
-
A.
canBeDeleted
Indicates that the referenced entity is eligible or permitted to be removed from the system.
-
B.
canBeRemovedBy
chosen
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
C.
canBeDeactivatedBy
Indicates that one entity has the ability or means to deactivate or disable another entity.
-
D.
canDestroy
Indicates that one entity has the ability or power to destroy another entity.
-
E.
canBeAbolishedBy
Indicates that one entity has the authority or power to formally end, revoke, or eliminate 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 1, 2026, 1:36 a.m.