Triple
T37415583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dell G5 |
E929695
|
entity |
| Predicate | hasDisplaySizeOption |
P13749
|
FINISHED |
| Object | 15.6‑inch display |
—
|
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: 15.6‑inch display | Statement: [Dell G5, hasDisplaySizeOption, 15.6‑inch display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplaySizeOption Context triple: [Dell G5, hasDisplaySizeOption, 15.6‑inch display]
-
A.
availableDisplaySizes
chosen
Indicates the set of display size options that can be provided or used for a given entity.
-
B.
supportsDisplayResolution
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
C.
hasPhysicalDisplays
Indicates that an entity possesses one or more tangible, visible display units or interfaces.
-
D.
coverDisplaySize
Indicates the size of a device’s secondary (cover) display in physical units, such as inches or centimeters.
-
E.
hasTopScreenSize
Indicates that an entity (typically a device) possesses a top screen with a specified size or dimension.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:16 p.m.