Triple
T13097278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3120 |
E310622
|
entity |
| Predicate | supportsChangeableCovers |
P105880
|
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 3120, supportsChangeableCovers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChangeableCovers Context triple: [Nokia 3120, supportsChangeableCovers, yes]
-
A.
supportsCustomCovers
chosen
Indicates that one entity provides the capability for another entity to use or define custom cover designs or images.
-
B.
hasCoverType
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
C.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
D.
hasUniversalCover
Indicates that one mathematical space serves as the universal covering space of another, mapping onto it via a covering map that is simply connected and covers all its loops.
-
E.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.