Triple
T25535333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silk Browser |
E640024
|
entity |
| Predicate | usesCloudInfrastructure |
P162084
|
FINISHED |
| Object | Amazon Web Services |
—
|
NE NERFINISHED |
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: Amazon Web Services | Statement: [Silk Browser, usesCloudInfrastructure, Amazon Web Services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCloudInfrastructure Context triple: [Silk Browser, usesCloudInfrastructure, Amazon Web Services]
-
A.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
B.
usesCloudTechnologyFrom
chosen
Indicates that one entity employs or relies on cloud-based technology, services, or infrastructure provided by another entity.
-
C.
typeOfCloud
Indicates the specific category or classification of a cloud within a cloud-type taxonomy or system.
-
D.
cloudBased
Indicates that something is hosted, delivered, or operates via cloud computing infrastructure rather than on local hardware.
-
E.
ownerOfInfrastructureUsed
Indicates that one entity owns the infrastructure that is being used by another entity or activity.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 3:22 p.m.