Triple
T35149793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E75 |
E1014952
|
entity |
| Predicate | hasFormFactorDetail |
P196400
|
FINISHED |
| Object | side-sliding 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: side-sliding keyboard | Statement: [Nokia E75, hasFormFactorDetail, side-sliding keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormFactorDetail Context triple: [Nokia E75, hasFormFactorDetail, side-sliding keyboard]
-
A.
hasFormFactor
Indicates that one entity possesses or is characterized by a particular physical or structural form factor defined by another entity.
-
B.
supportsFormFactorFamily
Indicates that one entity is compatible with and can operate using a specified family of physical or design form factors.
-
C.
targetFormFactor
Indicates the specific physical configuration or design format that something is intended to be used with or fit into.
-
D.
supportsDriveFormFactor
Indicates that one entity is compatible with or can accommodate a specified physical form factor of a drive.
-
E.
deviceShape
Indicates that one entity has the physical form or geometric configuration specified by the other entity.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69fe30bb07d08190877539d5aa202d24 |
completed | May 8, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:02 p.m.