Triple
T36752021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore Amiga 1200 |
E907937
|
entity |
| Predicate | alsoSoldBy |
P186264
|
FINISHED |
| Object | Escom |
—
|
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: Escom | Statement: [Commodore Amiga 1200, alsoSoldBy, Escom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoSoldBy Context triple: [Commodore Amiga 1200, alsoSoldBy, Escom]
-
A.
alsoSoldAs
Indicates that one item is marketed or available under an alternative name, label, or product identity.
-
B.
soldAt
Indicates that a product or item is offered for sale at a particular location, venue, or outlet.
-
C.
soldFrom
Indicates that something was transferred in a sale originating from a particular source, such as a seller, location, or organization.
-
D.
isSoldIn
Indicates that a product or item is available for purchase within a specified location, market, or sales channel.
-
E.
plansSoldBy
Indicates that one entity is the seller or provider of plans that are purchased or obtained by another entity.
- F. None of above. chosen
Provenance (4 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.