Triple
T27589196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VPN-as-a-service |
E699754
|
entity |
| Predicate | isDeliveredOver |
P130074
|
FINISHED |
| Object | internet |
—
|
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: internet | Statement: [VPN-as-a-service, isDeliveredOver, internet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeliveredOver Context triple: [VPN-as-a-service, isDeliveredOver, internet]
-
A.
isDeliveredThrough
chosen
Indicates that something is transmitted, conveyed, or provided by means of a specified channel, method, or medium.
-
B.
deliveredAs
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
C.
delivered
Indicates that something has been brought or transported to a recipient or destination, typically completing a transfer or fulfillment of an order, message, or service.
-
D.
deliveredBy
Indicates that something (such as a product, message, or service) is brought, transported, or provided to its destination by a specified agent or carrier.
-
E.
deliveredBefore
Indicates that one delivery event occurred earlier in time than another delivery event.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:05 p.m.