Triple
T13894487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BlackBerry Bold series |
E334052
|
entity |
| Predicate | typicalInputMethod |
P16221
|
FINISHED |
| Object | physical QWERTY keyboard |
—
|
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: physical QWERTY keyboard | Statement: [BlackBerry Bold series, typicalInputMethod, physical QWERTY keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInputMethod Context triple: [BlackBerry Bold series, typicalInputMethod, physical QWERTY keyboard]
-
A.
hasTypingFeature
Indicates that an entity possesses or supports a particular typing-related characteristic or capability.
-
B.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
C.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
-
D.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
-
E.
hasKeyboard
chosen
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a741908190bdf46d76c5f1411a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.