Triple
T1632055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Caching |
E35276
|
entity |
| Predicate | canBeBypassedBy |
P12840
|
FINISHED |
| Object | no-store directive |
—
|
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: no-store directive | Statement: [HTTP Caching, canBeBypassedBy, no-store directive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBypassedBy Context triple: [HTTP Caching, canBeBypassedBy, no-store directive]
-
A.
hasBypass
chosen
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
-
B.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
C.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
D.
canBePerformed
Indicates that a particular action or activity is possible to carry out under given conditions or by a specified agent.
-
E.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.