Triple
T9632413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP Spectre |
E232838
|
entity |
| Predicate | typicalScreenSizeRange |
P13474
|
FINISHED |
| Object | 13-inch to 16-inch |
—
|
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: 13-inch to 16-inch | Statement: [HP Spectre, typicalScreenSizeRange, 13-inch to 16-inch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScreenSizeRange Context triple: [HP Spectre, typicalScreenSizeRange, 13-inch to 16-inch]
-
A.
typicalPanelSize
Indicates the usual or standard dimensions associated with a given panel.
-
B.
availableDisplaySizes
Indicates the set of display size options that can be provided or used for a given entity.
-
C.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
D.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
E.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2783b48190a9929dc3e3cd2956 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.