Triple
T26792492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASDAQ: AMZN |
E670552
|
entity |
| Predicate | issuerCloudWebsite |
P69
|
FINISHED |
| Object | https://aws.amazon.com |
—
|
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: https://aws.amazon.com | Statement: [NASDAQ: AMZN, issuerCloudWebsite, https://aws.amazon.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerCloudWebsite Context triple: [NASDAQ: AMZN, issuerCloudWebsite, https://aws.amazon.com]
-
A.
applicationSite
Indicates the location or surface where a substance, treatment, or action is applied to an entity.
-
B.
integrationSite
Indicates the specific location or context where one entity is incorporated or embedded into another.
-
C.
website
chosen
Indicates that one entity is the official website or web presence associated with another entity.
-
D.
documentationHosting
Indicates that one entity provides a platform or service for storing, displaying, or serving the documentation of another entity.
-
E.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 4:17 a.m.