Triple
T5379857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compaq Presario |
E113053
|
entity |
| Predicate | typicalDisplaySizeRangeInches |
P13749
|
FINISHED |
| Object | 14–17 |
—
|
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: 14–17 | Statement: [Compaq Presario, typicalDisplaySizeRangeInches, 14–17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDisplaySizeRangeInches Context triple: [Compaq Presario, typicalDisplaySizeRangeInches, 14–17]
-
A.
availableDisplaySizes
chosen
Indicates the set of display size options that can be provided or used for a given entity.
-
B.
typicalPanelSize
Indicates the usual or standard dimensions associated with a given panel.
-
C.
integratedDisplaySize
Indicates the size or dimensions of a built-in or non-detachable display associated with an 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.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.