Triple
T37149862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic Keyboard for iPad Pro 11‑inch |
E920333
|
entity |
| Predicate | designedForScreenSize |
P9494
|
FINISHED |
| Object | 11‑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: 11‑inch | Statement: [Magic Keyboard for iPad Pro 11‑inch, designedForScreenSize, 11‑inch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForScreenSize Context triple: [Magic Keyboard for iPad Pro 11‑inch, designedForScreenSize, 11‑inch]
-
A.
developedForScreenBy
Indicates that one party adapted or created a work specifically for presentation on a screen-based medium (such as film, television, or digital video) on behalf of another.
-
B.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
screenDiameter
Indicates the size of a screen measured across its diagonal.
-
D.
hasTopScreenSize
Indicates that an entity (typically a device) possesses a top screen with a specified size or dimension.
-
E.
screenCapacity
Indicates the maximum number of items or content units that can be displayed on a screen at one time.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:15 p.m.