Triple
T19729446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soylent |
E473811
|
entity |
| Predicate | isSoldThrough |
P64619
|
FINISHED |
| Object | online retailers |
—
|
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: online retailers | Statement: [Soylent, isSoldThrough, online retailers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSoldThrough Context triple: [Soylent, isSoldThrough, online retailers]
-
A.
isSoldIn
Indicates that a product or item is available for purchase within a specified location, market, or sales channel.
-
B.
isDistributedThrough
chosen
Indicates that something is supplied, circulated, or made available to others via a particular channel, medium, or distribution mechanism.
-
C.
notSoldIn
Indicates that a product or item is unavailable for purchase within a specified market, region, or sales channel.
-
D.
plansSoldBy
Indicates that one entity is the seller or provider of plans that are purchased or obtained by another entity.
-
E.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fb27c48190893bfbc1018f12e2 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.