Triple
T13014228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E71 |
E322502
|
entity |
| Predicate | messagingFeatures |
P106275
|
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 E71, messagingFeatures, push email]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messagingFeatures Context triple: [Nokia E71, messagingFeatures, push email]
-
A.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
B.
hasMessenger
Indicates that one entity uses or is associated with another entity as a messenger or intermediary for communication.
-
C.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
D.
supportsNokiaMessaging
chosen
Indicates that an entity provides compatibility with or functionality for Nokia Messaging services.
-
E.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecbb8f4819094d55eb07cb5ad97 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:50 p.m.