Triple
T37707159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia XR20 |
E939225
|
entity |
| Predicate | softwareSupportPolicy |
P100244
|
FINISHED |
| Object | 3 years of Android OS upgrades |
—
|
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: 3 years of Android OS upgrades | Statement: [Nokia XR20, softwareSupportPolicy, 3 years of Android OS upgrades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareSupportPolicy Context triple: [Nokia XR20, softwareSupportPolicy, 3 years of Android OS upgrades]
-
A.
softwarePolicy
chosen
Indicates that there is a rule, guideline, or policy governing the use, development, or management of software in relation to the associated entities.
-
B.
supportPolicy
Indicates that one entity endorses, backs, or helps to maintain a particular policy or course of action.
-
C.
softwareHelpPage
Indicates that a software application provides a dedicated help or support page for users.
-
D.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
E.
supportRules
Indicates that one entity provides justification, backing, or validation for the rules or constraints 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.