Triple
T11657806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia Asha Platform |
E277052
|
entity |
| Predicate | supportsThirdPartyApps |
P31926
|
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 Asha Platform, supportsThirdPartyApps, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsThirdPartyApps Context triple: [Nokia Asha Platform, supportsThirdPartyApps, yes]
-
A.
supportsThirdPartyApplications
chosen
Indicates that an entity is capable of working with, integrating, or allowing the use of software applications developed by external third parties.
-
B.
allowsPerAppSettings
Indicates that an entity provides or supports configuration settings that can be customized separately for each individual application.
-
C.
thirdParty
Indicates that an entity is a separate, external party involved in a relationship or transaction between two primary entities.
-
D.
supports64BitApps
Indicates that the subject is capable of running or is compatible with 64-bit applications.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.