Triple
T7032868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Classmate PC |
E163310
|
entity |
| Predicate | screenSizeRange |
P13749
|
FINISHED |
| Object | 7-inch to 10-inch displays |
—
|
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: 7-inch to 10-inch displays | Statement: [Intel Classmate PC, screenSizeRange, 7-inch to 10-inch displays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenSizeRange Context triple: [Intel Classmate PC, screenSizeRange, 7-inch to 10-inch displays]
-
A.
availableDisplaySizes
chosen
Indicates the set of display size options that can be provided or used for a given entity.
-
B.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
C.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
D.
hasTopScreenSize
Indicates that an entity (typically a device) possesses a top screen with a specified size or dimension.
-
E.
integratedDisplaySize
Indicates the size or dimensions of a built-in or non-detachable display associated with an entity.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.