Triple
T12889144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E61 |
E308310
|
entity |
| Predicate | supportsNokiaIntellisync |
P107287
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nokia E61, supportsNokiaIntellisync, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNokiaIntellisync Context triple: [Nokia E61, supportsNokiaIntellisync, yes]
-
A.
supportsNokiaMessaging
Indicates that an entity provides compatibility with or functionality for Nokia Messaging services.
-
B.
supportsExchangeActiveSync
Indicates that one entity enables or is compatible with the use of Exchange ActiveSync for synchronization or communication with another entity.
-
C.
supportsPhoneBook
Indicates that an entity provides functionality for managing or accessing a phone book or contact list.
-
D.
supportsTransportIntegrationWith
Indicates that one entity enables or is compatible with the integration of transport or transportation-related systems, services, or data with another entity.
-
E.
supportsSIMInstruction
Indicates that one entity is capable of handling or executing a specified SIM (Subscriber Identity Module) instruction for another 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714581988190afc720ffd7797860 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:39 p.m.