Triple
T11973380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6230 |
E284974
|
entity |
| Predicate | supportsEmailProtocols |
P35980
|
FINISHED |
| Object | POP3 |
—
|
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: POP3 | Statement: [Nokia 6230, supportsEmailProtocols, POP3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEmailProtocols Context triple: [Nokia 6230, supportsEmailProtocols, POP3]
-
A.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
supportsPort
Indicates that one entity is capable of handling, providing, or being compatible with a specified port or port configuration.
-
C.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
D.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
E.
supportsSMS
Indicates that one entity provides the capability for another entity to send, receive, or otherwise use SMS (Short Message Service) messaging.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9039107e48190ae4c4efd6257dd3c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.