Triple
T8470767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple LaserWriter |
E200273
|
entity |
| Predicate | printingResolution |
P83492
|
FINISHED |
| Object | 300 dpi |
—
|
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: 300 dpi | Statement: [Apple LaserWriter, printingResolution, 300 dpi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printingResolution Context triple: [Apple LaserWriter, printingResolution, 300 dpi]
-
A.
printingColor
Indicates that one entity uses or displays a specific color in the context of printing or printed output.
-
B.
printingMethod
Indicates the technique or process used to produce a printed item or image.
-
C.
sensorResolution
Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
-
D.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
E.
printingCenter
Indicates a relationship where one entity serves as the printing center (i.e., the facility or service that performs printing) for 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_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. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:11 p.m.