Triple
T26792477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASDAQ: AMZN |
E670552
|
entity |
| Predicate | issuerOperatesDeviceBrand |
P32898
|
FINISHED |
| Object | Amazon Kindle |
—
|
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 Kindle | Statement: [NASDAQ: AMZN, issuerOperatesDeviceBrand, Amazon Kindle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerOperatesDeviceBrand Context triple: [NASDAQ: AMZN, issuerOperatesDeviceBrand, Amazon Kindle]
-
A.
issuerOperatesService
Indicates that an issuer is responsible for operating or running a particular service.
-
B.
issuerOperatesIn
Indicates that an issuing entity conducts business activities or has operational presence within a specified geographic area or jurisdiction.
-
C.
issuerBrandPortfolioIncludes
Indicates that an issuer’s overall brand portfolio contains or encompasses a particular brand.
-
D.
operatedByBrand
chosen
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
E.
issuerBrandName
Indicates the brand name associated with the entity that issues a product, document, or instrument.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 4:17 a.m.