Triple
T20221352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 6 Plus |
E495260
|
entity |
| Predicate | screenCategory |
P139272
|
FINISHED |
| Object | phablet |
—
|
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: phablet | Statement: [iPhone 6 Plus, screenCategory, phablet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenCategory Context triple: [iPhone 6 Plus, screenCategory, phablet]
-
A.
navigationCategory
Indicates that one entity is classified under, or associated with, a particular navigation-related category used for organizing or guiding access to content or locations.
-
B.
playsCategory
Indicates that an entity engages in or performs activities belonging to a specified category.
-
C.
televisionCategory
Indicates the classification or genre category assigned to a television-related entity (such as a show, channel, or program).
-
D.
streamingCategory
Indicates the classification or genre under which a piece of content is organized or presented on a streaming platform.
-
E.
screensAt
Indicates that one entity shows, projects, or displays another entity (such as a film, program, or content) on a screen or at a screening venue.
- F. None of above. chosen
Provenance (4 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd610f881908fdd22b1f8bd2efc |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:39 p.m.