Triple
T38697937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia Belle |
E950055
|
entity |
| Predicate | availableAsUpdateFor |
P93033
|
FINISHED |
| Object | Nokia N8 |
—
|
NE NERFINISHED |
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: Nokia N8 | Statement: [Nokia Belle, availableAsUpdateFor, Nokia N8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableAsUpdateFor Context triple: [Nokia Belle, availableAsUpdateFor, Nokia N8]
-
A.
softwareUpdatable
Indicates that a software system or component can be modified or upgraded after deployment, typically through patches, updates, or new versions.
-
B.
upgradeAppliesTo
chosen
Indicates that a particular upgrade is applicable to, or can be applied to, a specified target entity.
-
C.
upgradeEligibility
Indicates whether an entity qualifies to move from its current version, level, or plan to a higher or more advanced one under defined criteria.
-
D.
isUpdateFor
Indicates that one entity serves as a newer or modified version that replaces or revises another entity.
-
E.
updatesFrom
Indicates that one entity is revised, modified, or brought to a newer state based on information, changes, or content originating from 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:33 p.m.