Triple
T12969601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E70 |
E321357
|
entity |
| Predicate | emailTechnologies |
P76504
|
FINISHED |
| Object | Push email |
—
|
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: Push email | Statement: [Nokia E70, emailTechnologies, Push email]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emailTechnologies Context triple: [Nokia E70, emailTechnologies, Push email]
-
A.
technologyUsedBy
chosen
Indicates that a particular technology is employed or utilized by a specified entity.
-
B.
supportsPushEmail
Indicates that one entity provides or enables automatic, real-time delivery of email (push email) to another entity.
-
C.
technologyStack
Indicates the set of technologies, tools, and platforms used together to build or run a system, application, or project.
-
D.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
E.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:34 p.m.