Triple
T8610305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cache Storage API |
E203898
|
entity |
| Predicate | exposedOn |
P14188
|
FINISHED |
| Object | Window interface |
—
|
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: Window interface | Statement: [Cache Storage API, exposedOn, Window interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposedOn Context triple: [Cache Storage API, exposedOn, Window interface]
-
A.
exposedDuring
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
-
B.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
C.
exposed
chosen
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
D.
exposedAs
Indicates that one entity reveals or publicly identifies another entity as having a hidden, false, or previously concealed role, identity, or nature.
-
E.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ee96ac8190809817c403da2889 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.