Triple

T21741609
Position Surface form Disambiguated ID Type / Status
Subject 12.9‑inch iPad Pro (1st generation) E536671 entity
Predicate supportsSplitViewMultitasking P98963 FINISHED
Object true 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: true | Statement: [12.9‑inch iPad Pro (1st generation), supportsSplitViewMultitasking, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsSplitViewMultitasking
Context triple: [12.9‑inch iPad Pro (1st generation), supportsSplitViewMultitasking, true]
  • A. supportsSplitScreen chosen
    Indicates that one entity enables or is compatible with displaying multiple views or applications simultaneously in a split-screen layout.
  • B. multitaskingSupport
    Indicates that an entity is capable of performing multiple tasks or operations concurrently or in parallel.
  • C. supportsMultipleWindows
    Indicates that the subject can handle or display more than one window or view simultaneously.
  • D. supportsView
    Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
  • E. supportsMultipleTerminals
    Indicates that an entity is capable of handling or operating with more than one terminal or endpoint simultaneously.
  • 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_69e0c46df5448190b4322127ffc4c690 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a7250d48190aa63f89db017ef70 completed April 28, 2026, 2:24 a.m.
PD Predicate disambiguation batch_69e6969c16fc8190b5126c169317d85d completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:49 p.m.