Triple
T8470776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple LaserWriter |
E200273
|
entity |
| Predicate | companyProductLine |
P40829
|
FINISHED |
| Object | Apple printer products |
—
|
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: Apple printer products | Statement: [Apple LaserWriter, companyProductLine, Apple printer products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyProductLine Context triple: [Apple LaserWriter, companyProductLine, Apple printer products]
-
A.
productLineStart
Indicates the point in time or position at which a particular product line begins or is first introduced.
-
B.
belongsToProductLine
chosen
Indicates that an item or product is associated with and classified under a specific product line.
-
C.
associatedCompanyMainProductLine
Indicates that a company’s primary or main line of products is linked or related to a specified product category or product line.
-
D.
productFamily
Indicates that one product belongs to, or is categorized under, a broader product family or line.
-
E.
usedInProductLine
Indicates that something (such as a component, material, or feature) is utilized within a particular product line.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.